From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: Asynchronous scsi scanning Date: Tue, 15 May 2007 19:59:39 -0700 Message-ID: References: <1179153096.3703.23.camel@mulgrave.il.steeleye.com> <17841.simon.1179228389@5ec7c279.invalid> <20070515120228.GI10562@parisc-linux.org> <4649E03A.1090004@simon.arlott.org.uk> <20070515172905.GJ10562@parisc-linux.org> <20070516025121.GK10562@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from sj-iport-3-in.cisco.com ([171.71.176.72]:48045 "EHLO sj-iport-3.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755557AbXEPC7p (ORCPT ); Tue, 15 May 2007 22:59:45 -0400 In-Reply-To: <20070516025121.GK10562@parisc-linux.org> (Matthew Wilcox's message of "Tue, 15 May 2007 20:51:21 -0600") Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Matthew Wilcox Cc: Satyam Sharma , Simon Arlott , James Bottomley , Dave Jones , Linux Kernel Mailing List , linux-scsi@vger.kernel.org, kernel-packagers@vger.kernel.org, "Robert P. J. Day" > 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.