[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc43514a0907151312l34bc6c92m7986fd1f99cfca2c@mail.gmail.com>
Date: Wed, 15 Jul 2009 22:12:55 +0200
From: Andreas Robinson <andr345@...il.com>
To: Michal Marek <mmarek@...e.cz>
Cc: Kay Sievers <kay.sievers@...y.org>,
Scott James Remnant <scott@...ntu.com>,
linux-modules@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kbuild: generate modules.builtin
On Wed, Jul 15, 2009 at 9:08 PM, Michal Marek<mmarek@...e.cz> wrote:
> Andreas Robinson napsal(a):
>> Guys,
>>
>> is this patch what you need on the m-i-t end?
>
> I already have patches here (it's not against Jon's master, but it
> should apply):
> http://repo.or.cz/w/mit.git?a=commit;h=45c29de1b54478a63352a3f13c570a964903f54f
> http://repo.or.cz/w/mit.git?a=commit;h=0e72912a1e0b486225f7052c8d40e28b07ff4495
Ah, of course!
> 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.
Andreas
--
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