From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
pefoley2@verizon.net, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild fixes for 3.0
Date: Fri, 10 Jun 2011 14:13:28 +0200 [thread overview]
Message-ID: <4DF20A68.2090307@suse.cz> (raw)
In-Reply-To: <BANLkTinQ2mL1eNPzMHjDjXnLyv58annZmA@mail.gmail.com>
On 10.6.2011 05:57, Linus Torvalds wrote:
> On Thu, Jun 9, 2011 at 8:45 PM, Arnaud Lacombe<lacombar@gmail.com> wrote:
>>
>> For the record, this should have been fixed by Michal in:
>
> You're missing the problem: we can't assume that people have updated user land.
>
> Furthermore, the very pull request I'm responding to actually tries to
> handle this, see commit bfe5424a8b31 ("kbuild: Hack for depmod not
> handling X.Y versions"), but it's just not working for me.
It handles what can be handled inside the kernel build, i.e. the depmod
called from the Makefile during modules_install.
> And it's not working, because it only handles the "modules_install"
> case, not the case where the system install scripts do their own
> depmod.
Yes, tools creating an initrd would need a similar workaround, that's a
pity :-(.
Michal
prev parent reply other threads:[~2011-06-10 12:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 21:42 [GIT] kbuild fixes for 3.0 Michal Marek
2011-06-10 0:10 ` Linus Torvalds
2011-06-10 3:14 ` Arnaud Lacombe
2011-06-10 3:37 ` Linus Torvalds
2011-06-10 3:41 ` Arnaud Lacombe
2011-06-10 3:45 ` Arnaud Lacombe
2011-06-10 3:57 ` Linus Torvalds
2011-06-10 5:16 ` Arnaud Lacombe
2011-06-10 5:53 ` Ray Lee
2011-06-10 10:03 ` maximilian attems
2011-06-10 15:22 ` Linus Torvalds
2011-06-10 20:45 ` Michal Marek
2011-06-10 20:56 ` Linus Torvalds
2011-06-10 15:06 ` Andy Whitcroft
2011-06-10 15:26 ` Milan Broz
2011-06-10 16:30 ` Arnaud Lacombe
2011-06-10 19:31 ` [lm-sensors] " Jean Delvare
2011-06-10 12:13 ` 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=4DF20A68.2090307@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@verizon.net \
--cc=torvalds@linux-foundation.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