From: David Ahern <dsa@cumulusnetworks.com>
To: linux-mips@linux-mips.org
Subject: Fwd: Re: [PATCH net-next 3/5] net: Refactor path selection in __ip_route_output_key
Date: Fri, 2 Oct 2015 10:04:03 -0600 [thread overview]
Message-ID: <560EAAF3.3040509@cumulusnetworks.com> (raw)
In-Reply-To: <201510021431.hGNWKbMp%fengguang.wu@intel.com>
Hello:
I could use some help understanding a message from a kbuild robot. I
submitted this patch:
https://patchwork.ozlabs.org/patch/525102/
Which moves existing code into a function that is exported for modules.
The kbuild robot found this warning:
-----
config: mips-nlm_xlp_defconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=mips
All warnings (new ones prefixed by >>):
>> mips-linux-gnu-ld: net/ipv4/.tmp_fib_semantics.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
-----
I have no idea what that message means. I tried googling and found this
recent thread:
http://www.linux-mips.org/archives/linux-mips/2015-05/msg00156.html
and accompanying one:
https://sourceware.org/bugzilla/show_bug.cgi?id=18401
Can someone shed light on what the message means, why my patch generated
the message and better yet how to fix it?
Thanks,
David
next parent reply other threads:[~2015-10-02 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1443713247-11230-4-git-send-email-dsa@cumulusnetworks.com>
[not found] ` <201510021431.hGNWKbMp%fengguang.wu@intel.com>
2015-10-02 16:04 ` David Ahern [this message]
2015-10-05 10:11 ` Fwd: Re: [PATCH net-next 3/5] net: Refactor path selection in __ip_route_output_key Joshua Kinard
[not found] ` <20151005.063836.1612675139838377064.davem@davemloft.net>
2015-10-05 14:08 ` David Ahern
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=560EAAF3.3040509@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=linux-mips@linux-mips.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