> No, it does matter. Your suggestion doesn't work, because > /sys/module/scsi_mod/parameters/ belongs to the module code. To create > a new attribute there, you use the module_param() code -- and there's > no way to have code called when your parameter is changed. If I'm not misunderstanding what you're talking about, there is actually a way to have code called when a module parameter is changed: module_param_call(). - R. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: why does x86 "make defconfig" build a single, lonely module?
- From: "Satyam Sharma" <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
- From: "Satyam Sharma" <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
- From: "Satyam Sharma" <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
- From: James Bottomley <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
- From: "Satyam Sharma" <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
- From: "Simon Arlott" <[email protected]>
- Asynchronous scsi scanning
- From: Matthew Wilcox <[email protected]>
- Re: Asynchronous scsi scanning
- From: Simon Arlott <[email protected]>
- Re: Asynchronous scsi scanning
- From: Matthew Wilcox <[email protected]>
- Re: Asynchronous scsi scanning
- From: "Satyam Sharma" <[email protected]>
- Re: Asynchronous scsi scanning
- From: Matthew Wilcox <[email protected]>
- Re: why does x86 "make defconfig" build a single, lonely module?
- Prev by Date: Re: Asynchronous scsi scanning
- Next by Date: Pagecache zeroing: zero_user_segment, zero_user_segments and zero_user
- Previous by thread: Re: Asynchronous scsi scanning
- Next by thread: Re: Asynchronous scsi scanning
- Index(es):
 |