From: Andreas Gruenbacher <agruen@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modules_install must not remove existing modules
Date: Thu, 6 Apr 2006 00:21:36 +0200 [thread overview]
Message-ID: <200604060021.37049.agruen@suse.de> (raw)
In-Reply-To: <20060405221229.GA8972@mars.ravnborg.org>
On Thursday 06 April 2006 00:12, Sam Ravnborg wrote:
> The removal was introduced to get rid of old modules from an earlier
> build of the same kernel with potential more modules.
> I was obvious when I played with an allmodconfig kernel IIRC.
The in-tree modules all install below kernel/, so I don't see why removing the
external modules directory (extra or whatever) is necessary for that. It
might still be that there are other external modules
below /lib/modules/$KERNELRELEASE, though.
> The usecase you have in mind is with external modules only?
Yes, with more than one set of them, each of which using modules_install.
> We could special case in that suation and avoid the removal.
>
> I see no way to detect when it is OK to remove or not, so in the
> principle of least suprise I prefer having the removal unconditional for
> normal kernel builds, and no removal for external modules.
>
> OK?
That would be okay for me, yes.
Thanks,
Andreas
next prev parent reply other threads:[~2006-04-05 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 21:33 [PATCH] modules_install must not remove existing modules Andreas Gruenbacher
2006-04-05 21:52 ` Valdis.Kletnieks
2006-04-05 22:06 ` Andreas Gruenbacher
2006-04-05 22:33 ` Gene Heskett
2006-04-05 22:12 ` Sam Ravnborg
2006-04-05 22:21 ` Andreas Gruenbacher [this message]
2006-04-06 4:04 ` Valdis.Kletnieks
2006-04-06 6:43 ` Sam Ravnborg
2006-04-06 20:28 ` Randy.Dunlap
2006-04-06 20:29 ` Sam Ravnborg
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=200604060021.37049.agruen@suse.de \
--to=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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