All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Giacomo A. Catenazzi" <cate@cateee.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: akpm@linux-foundation.org, sam@ravnborg.org,
	linux-kbuild@vger.kernel.org, adobriyan@gmail.com,
	zippel@linux-m68k.org
Subject: Re: [patch 12/13] kconfig: add module_name shortcut
Date: Thu, 30 Oct 2008 12:16:01 +0100	[thread overview]
Message-ID: <49099771.8000302@cateee.net> (raw)
In-Reply-To: <20081030110211.GA25873@cs181140183.pp.htv.fi>

Adrian Bunk wrote:
> On Wed, Oct 29, 2008 at 02:20:14PM -0700, akpm@linux-foundation.org wrote:
>> From: Alexey Dobriyan <adobriyan@gmail.com>
>>
>> Add Kconfig token "module_name" to supply module's name. Example:
>>
>> 	config FOO
>> 		tristate "foo"
>> 		module_name foo
>> 		---help---
>> 		  foo
>>
>> Print module's name as following on menuconfigs help screen (press 'h'):
>>
>> 	Module name: foo
>>
>> 8139too driver converted to show real-life example.
>>
>> P.S.: menuconfig only, no checking wrt modular/standalone code et al.
>> ...
> 
> We have 4 interfaces, and for not losing information all of them have to 
> support it.
> 
>> --- a/drivers/net/Kconfig~kconfig-add-module_name-shortcut
>> +++ a/drivers/net/Kconfig
>> @@ -1549,14 +1549,12 @@ config 8139TOO
>>  	depends on NET_PCI && PCI
>>  	select CRC32
>>  	select MII
>> +	module_name 8139too
>>  	---help---
>>  	  This is a driver for the Fast Ethernet PCI network cards based on
>>  	  the RTL 8129/8130/8139 chips. If you have one of those, say Y and
>>  	  read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
>>  
>> -	  To compile this driver as a module, choose M here: the module
>> -	  will be called 8139too.  This is recommended.
>> -
>> ...
> 
> Are you planning any further usage of the module_name?
> 
> Currently your patch seems to be in menuconfig equivalent to
> 
> -       To compile this driver as a module, choose M here: the module
> -       will be called 8139too.  This is recommended.
> +	Module name: 8139too
> 
> I don't have any strong opinion whether that's better or worse, but if 
> that's the only change we don't need a new kconfig syntax for it.

This feature is very useful for auto configuration: from a lsmod you 
will find easily the relevant configuration.

Actually I'm doing it with some complexer scripts, but some Makefile
are "creative".

I had some plan to include more building information to Kconfig
to automatically generating some part of Makefile's.

ciao
	cate

  reply	other threads:[~2008-10-30 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 21:20 [patch 12/13] kconfig: add module_name shortcut akpm
2008-10-30 11:02 ` Adrian Bunk
2008-10-30 11:16   ` Giacomo A. Catenazzi [this message]
2008-10-30 11:31     ` Alexey Dobriyan
2008-10-30 12:00       ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49099771.8000302@cateee.net \
    --to=cate@cateee.net \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.