From: Vivek Goyal <vgoyal@in.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Thomas Meyer <thomas@m3y3r.de>,
linux-kernel@vger.kernel.org,
Fastboot mailing list <fastboot@lists.osdl.org>
Subject: Re: Section mismatch on current git head
Date: Wed, 3 Jan 2007 11:30:01 +0530 [thread overview]
Message-ID: <20070103060001.GB25433@in.ibm.com> (raw)
In-Reply-To: <20061222094710.1f29b39a.randy.dunlap@oracle.com>
On Fri, Dec 22, 2006 at 09:47:10AM -0800, Randy Dunlap wrote:
> On Fri, 22 Dec 2006 15:24:41 +0100 Thomas Meyer wrote:
>
> > Hello.
> >
> > What kind of problem is this:
> > 1.) the one that should be fixed, but also can be ignored or
> > 2.) the one that have to be fixed and ignorance is a bad idea?
> >
>
> Is this with CONFIG_RELOCATABLE=y?
> There were some patches posted to address section mismatches
> with that config option. I suppose that they will be in the
> next -mm release (?), so this needs to be retested with
> those patches applied.
>
Hi Randy,
I have posted some patches. But there are lots of warnings and I am
still working through the rest. Already posted patches are available
in rc2-mm1.
Any help from respective subsystem maintainers is appreciated. :-)
These problems are already present. CONFIG_RELOCATABLE=y just makes
them visible to MODPOST as relocatation information is retained in
vmlinux if CONFIG_RELOCATABLE=y.
Thanks
Vivek
next prev parent reply other threads:[~2007-01-03 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 14:24 Section mismatch on current git head Thomas Meyer
2006-12-22 17:47 ` Randy Dunlap
2007-01-03 6:00 ` Vivek Goyal [this message]
2006-12-23 5:40 ` Len Brown
2007-01-03 6:04 ` Vivek Goyal
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=20070103060001.GB25433@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=thomas@m3y3r.de \
/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