[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20080828123847.dfc8943b.akpm@linux-foundation.org>
Date: Thu, 28 Aug 2008 12:38:47 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: kernel1@...erdogtech.com
Cc: bugme-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 11446] New: Automate "to compile as module"
strings
On Thu, 28 Aug 2008 09:24:42 -0700 (PDT)
bugme-daemon@...zilla.kernel.org wrote:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=11446
>
> Summary: Automate "to compile as module" strings
> Product: Other
> Version: 2.5
> KernelVersion: 2.6.27
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: enhancement
> Priority: P1
> Component: Configuration
> AssignedTo: zippel@...ux-m68k.org
> ReportedBy: kernel1@...erdogtech.com
>
>
> I've spent quite a bit of time scanning through Kconfig files correcting
> various textual errors. One thing that I've noticed is variations of "To
> compile X as a module, choose M here. The module will be called Y" occur
> extremely frequently. A quick grep of the current mainline actually reveals
> ~1192 instances of it. It seems very redundant to me to have everyone who adds
> a module or feature copy and paste this text, when it could seemingly be
> dynamically generated with ease.
>
> Is there any reason we can't simply standardize on one string, and display it
> for any component that has the module option available?
Good point :)
The Kconfig system doesn't presently know the name of the module,
but that could be added. eg:
config BMAC
tristate "BMAC (G3 ethernet) support"
depends on PPC_PMAC && PPC32
+ modulename bmac
select CRC32
help
Say Y for support of BMAC Ethernet interfaces. These are used on G3
computers.
- To compile this driver as a module, choose M here: the module
- will be called bmac.
Any sane organisation would look at the benefit of this, weigh that
against the massive amount of code churn and would then run away howling.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists