From: Sam Ravnborg <sam@ravnborg.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
akpm@osdl.org, linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] Add module_name Kconfig shortcut
Date: Thu, 30 Oct 2008 22:04:34 +0100 [thread overview]
Message-ID: <20081030210434.GA1519@uranus.ravnborg.org> (raw)
In-Reply-To: <20081028004604.GA17144@x200.localdomain>
On Tue, Oct 28, 2008 at 03:46:04AM +0300, Alexey Dobriyan wrote:
> As correctly noticed in bug 11446 (http://bugzilla.kernel.org/show_bug.cgi?id=11446)
> "To compile this driver as a module, blah-blah" boilerplate is being
> copy-pasted to death with slight variations.
>
> 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.
Hi Alexey.
This is a baby step towards moving simple module stuff to Kconfig.
This is the way we want to go when someone cooks up proper support for that.
But we should do it in one go so when someone decide to visit the
8139too driver then they can do a full conversion to the "keep all
module definition in Kconfig" in one step.
Please see a few mails from Roman Zippel outlining his ideas.
I do not recall the details but I do recall that he suggested
to name the source files in Kconfig.
And when we do it we shall at least support it in menuconfig and xconfig.
config and gconfig can come later.
config and gconfig shall at least generate a correct config but may not
show all relavent info.
Sam
parent reply other threads:[~2008-10-30 21:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20081028004604.GA17144@x200.localdomain>]
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=20081030210434.GA1519@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox