From: Michal Marek <mmarek@suse.cz>
To: Andreas Robinson <andr345@gmail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Scott James Remnant <scott@ubuntu.com>,
linux-modules@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: generate modules.builtin
Date: Wed, 15 Jul 2009 22:16:14 +0200 [thread overview]
Message-ID: <4A5E390E.2040004@suse.cz> (raw)
In-Reply-To: <cc43514a0907151312l34bc6c92m7986fd1f99cfca2c@mail.gmail.com>
Andreas Robinson napsal(a):
> On Wed, Jul 15, 2009 at 9:08 PM, Michal Marek<mmarek@suse.cz> wrote:
>> The idea is that modprobe should just do nothing and exit successfully,
>> so that scripts don't break nor start printing warnings if the kernel
>> config changes. I meant to send it to linux-modules once there is
>> agreement about the modules.builtin file format.
>
> Ok, that makes sense.
>
> I think there's a small chance of confusion though, when a user tries
> to insert a module and it doesn't show up with lsmod. Perhaps you can
> add an info() message? Then the user can figure out what is happening
> with the --verbose option.
Good idea, will do that.
Michal
prev parent reply other threads:[~2009-07-15 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 15:25 [PATCH] kbuild: generate modules.builtin Michal Marek
2009-05-27 21:26 ` Kay Sievers
2009-05-27 21:38 ` Scott James Remnant
2009-07-03 14:45 ` Michal Marek
2009-07-15 16:39 ` Scott James Remnant
2009-07-15 16:46 ` Kay Sievers
2009-07-15 18:04 ` Andreas Robinson
2009-07-15 19:08 ` Michal Marek
2009-07-15 20:12 ` Andreas Robinson
2009-07-15 20:16 ` Michal Marek [this message]
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=4A5E390E.2040004@suse.cz \
--to=mmarek@suse.cz \
--cc=andr345@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=scott@ubuntu.com \
/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