From: ebiederm@xmission.com (Eric W. Biederman)
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Magnus Damm <magnus@valinux.co.jp>,
linux-kernel@vger.kernel.org, fastboot@lists.osdl.org
Subject: Re: [PATCH] CONFIG_RELOCATABLE modpost fix
Date: Tue, 08 Aug 2006 13:59:03 -0600 [thread overview]
Message-ID: <m17j1j6ltk.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060808183954.GA8300@mars.ravnborg.org> (Sam Ravnborg's message of "Tue, 8 Aug 2006 20:39:54 +0200")
Sam Ravnborg <sam@ravnborg.org> writes:
> On Tue, Aug 08, 2006 at 05:32:11PM +0900, Magnus Damm wrote:
>> CONFIG_RELOCATABLE modpost fix
>>
>> Run modpost on vmlinux regardless of CONFIG_MODULES.
> Below is my take on this one.
> - Dropped -rR since this is default now
> - Dropped subdir- assignment in scripts/Makefile since it is redundant
> - Always pass vmlinux ti modpost so we have full updated info
> - Print out number of modules being mod posted to distingush from
> vmlinux one
> - use vmlinux as target name to enable nicer quiet command print
Sam, Magnus:
I'm dense. Why do we want to run modpost if we are building a kernel
that doesn't support modules?
I haven't mucked with modpost at all so I don't have a good feel for
what it does, or why we want to run it.
My quick skimming says modpost is all about generating the module
version symbol scrambling. Which if that is all it does means it is
senseless to run this without modules.
Eric
next prev parent reply other threads:[~2006-08-08 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 8:32 Magnus Damm
2006-08-08 15:16 ` Sam Ravnborg
2006-08-09 1:12 ` Magnus Damm
2006-08-08 18:39 ` Sam Ravnborg
2006-08-08 19:59 ` Eric W. Biederman [this message]
2006-08-08 22:05 ` Sam Ravnborg
2006-08-09 1:32 ` Magnus Damm
2006-08-09 6:29 ` Sam Ravnborg
2006-08-09 7:06 ` Magnus Damm
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=m17j1j6ltk.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus@valinux.co.jp \
--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
Powered by JetHome