Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754029AbYAPM0j (ORCPT ); Wed, 16 Jan 2008 07:26:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752337AbYAPM0c (ORCPT ); Wed, 16 Jan 2008 07:26:32 -0500 Received: from ozlabs.org ([203.10.76.45]:49592 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752087AbYAPM0b (ORCPT ); Wed, 16 Jan 2008 07:26:31 -0500 From: Rusty Russell To: "rae l" Subject: Re: [RFC on MODULE SUPPORT] hello, Rusty, Should we provide module information even if the kernel module compiled built-in with bzImage? Date: Wed, 16 Jan 2008 23:25:54 +1100 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) Cc: open-iscsi@googlegroups.com, linux-kernel@vger.kernel.org References: <91b13c310801160202y833df7bs37cbb5827e875569@mail.gmail.com> In-Reply-To: <91b13c310801160202y833df7bs37cbb5827e875569@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801162325.54326.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 827 Lines: 25 On Wednesday 16 January 2008 21:02:22 rae l wrote: > hello, Rusty: Hi Denis. > Should we provide module information under > /sys/module//... even if the module compiled built-in > with bzImage? Absolutely. Module parameters (should) already do that, for example. > Or just this module(scsi_transport_iscsi) should be marked with [M] only? > > if the former solution is preferred, I would be happy to work on > MODULE_INFO-like macros improvements with CONFIG_MODULE undefined. I'd love to see patches. module_parm showed it's possible, if messy. Thanks! Rusty. -- 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/