From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: section mismatch warnings in current git head for powerpc
Date: Thu, 22 May 2008 19:50:08 +0200 [thread overview]
Message-ID: <e2e108260805221050s3ee280an8155898c216c334c@mail.gmail.com> (raw)
In-Reply-To: <4835ABDB.8020901@nortel.com>
On Thu, May 22, 2008 at 7:22 PM, Chris Friesen <cfriesen@nortel.com> wrote:
> I got the following warnings when building current git head for powerpc
> 64bit:
Something that should be fixed, but not something to worry about.
Similar warnings appear when building the kernel for x86_64. See also
http://lkml.org/lkml/2008/4/13/98, http://lkml.org/lkml/2008/4/17/202
and http://bugzilla.kernel.org/show_bug.cgi?id=9974.
Bart.
next prev parent reply other threads:[~2008-05-22 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 17:22 section mismatch warnings in current git head for powerpc Chris Friesen
2008-05-22 17:50 ` Bart Van Assche [this message]
2008-05-23 1:02 ` Michael Ellerman
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=e2e108260805221050s3ee280an8155898c216c334c@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).