On Mon, Jan 29, 2007 at 10:55:48AM +0100, Jiri Kosina wrote: > Changing module parameter values through sysfs is not a very nice idea, > because the change of the value is indeed silent - the driver is not > notified in any way, that the value has changed. So the driver should take > care of it by itself, which is not a nice thing. There is module_param_call() - used at least by drivers/md/md.c: static int get_ro(char *buffer, struct kernel_param *kp) ... static int set_ro(const char *val, struct kernel_param *kp) ... module_param_call(start_ro, set_ro, get_ro, NULL, S_IRUSR|S_IWUSR);
Attachment:
pgpsWNA9nnQrB.pgp
Description: PGP signature
- References:
- 2.6.20-rc6 pb_fnmode regression
- From: Soeren Sonnenburg <[email protected]>
- Re: 2.6.20-rc6 pb_fnmode regression
- From: Jiri Kosina <[email protected]>
- 2.6.20-rc6 pb_fnmode regression
- Prev by Date: Re: 2.6.20-rc6 pb_fnmode regression
- Next by Date: Re: [PATCH 3/3] lutimesat: actual syscall and wire-up on i386
- Previous by thread: Re: 2.6.20-rc6 pb_fnmode regression
- Next by thread: [PATCH] usbhid quirks for macbook(pro) updated to 2.6.20-rc6
- Index(es):