Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762259AbXEPDAF (ORCPT ); Tue, 15 May 2007 23:00:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755759AbXEPC7r (ORCPT ); Tue, 15 May 2007 22:59:47 -0400 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 X-IronPort-AV: i="4.14,538,1170662400"; d="scan'208"; a="486138928:sNHT46335210" 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" Subject: Re: Asynchronous scsi scanning X-Message-Flag: Warning: May contain useful information 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> From: Roland Dreier Date: Tue, 15 May 2007 19:59:39 -0700 In-Reply-To: <20070516025121.GK10562@parisc-linux.org> (Matthew Wilcox's message of "Tue, 15 May 2007 20:51:21 -0600") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 16 May 2007 02:59:39.0580 (UTC) FILETIME=[3E959FC0:01C79766] Authentication-Results: sj-dkim-4; header.From=rdreier@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 680 Lines: 15 > 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/