From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: shemminger@vyatta.com, netdev@vger.kernel.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
jchapman@katalix.com
Subject: Re: Section msimatch warnings
Date: Mon, 25 Oct 2010 16:27:24 -0700 (PDT) [thread overview]
Message-ID: <20101025.162724.71111412.davem@davemloft.net> (raw)
In-Reply-To: <20101026100427.f7c30b3d.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 26 Oct 2010 10:04:27 +1100
> This is actually different - it is generated by the compiler. I am not
> sure why we only get them on PowerPC.
I think it has to do with how function descriptors work on powerpc.
Code references to static (local) things work different from how
global scope references work.
prev parent reply other threads:[~2010-10-25 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 3:19 linux-next: build failure after merge of the final tree (net-current tree related) Stephen Rothwell
2010-10-25 5:26 ` David Miller
2010-10-25 17:36 ` Stephen Hemminger
2010-10-25 23:04 ` Section msimatch warnings (Was: Re: linux-next: build failure after merge of the final tree (net-current tree related)) Stephen Rothwell
2010-10-25 23:27 ` David Miller [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=20101025.162724.71111412.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jchapman@katalix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shemminger@vyatta.com \
/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).