[lkml]   [2008]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bugme-new] [Bug 11446] New: Automate "to compile as module" strings
On Thu, 28 Aug 2008 09:24:42 -0700 (PDT) wrote:

> 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:
> ReportedBy:
> 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
Say Y for support of BMAC Ethernet interfaces. These are used on G3

- 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.

 \ /
  Last update: 2008-08-28 21:43    [W:0.025 / U:70.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site