public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox•net>
To: kbuild test robot <lkp@intel•com>
Cc: kbuild-all@01•org, davem@davemloft•net,
	hannes@stressinduktion•org, ast@plumgrid•com,
	netdev@vger•kernel.org
Subject: Re: [PATCH net-next v2 1/5] net: move net_get_random_once to lib
Date: Thu, 08 Oct 2015 08:42:03 +0200	[thread overview]
Message-ID: <5616103B.2030805@iogearbox.net> (raw)
In-Reply-To: <201510081306.aKMKQcGQ%fengguang.wu@intel.com>

On 10/08/2015 07:12 AM, kbuild test robot wrote:
> Hi Hannes,
>
> [auto build test WARNING on net-next/master -- if it's inappropriate base, please ignore]
>
> config: mips-ip27_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: lib/lockref.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
>     mips-linux-gnu-ld: lib/lockref.o: warning: Inconsistent ISA extensions between e_flags and .MIPS.abiflags
[...]
>     mips-linux-gnu-ld: lib/reciprocal_div.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
>     mips-linux-gnu-ld: lib/reciprocal_div.o: warning: Inconsistent ISA extensions between e_flags and .MIPS.abiflags
>>> mips-linux-gnu-ld: lib/once.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
>>> mips-linux-gnu-ld: lib/once.o: warning: Inconsistent ISA extensions between e_flags and .MIPS.abiflags

Looks like a known issue on MIPS given the warning is not new also on other object
files. Here was what was discussed recently on this subject on a refactoring patch
from David Ahern:

   https://patchwork.ozlabs.org/patch/525102/

Thanks!

>     mips-linux-gnu-ld: lib/string_helpers.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
>     mips-linux-gnu-ld: lib/string_helpers.o: warning: Inconsistent ISA extensions between e_flags and .MIPS.abiflags
[...]

  reply	other threads:[~2015-10-08  6:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 23:20 [PATCH net-next v2 0/5] BPF/random32 updates Daniel Borkmann
2015-10-07 23:20 ` [PATCH net-next v2 1/5] net: move net_get_random_once to lib Daniel Borkmann
2015-10-07 23:55   ` Alexei Starovoitov
2015-10-08  5:12   ` kbuild test robot
2015-10-08  6:42     ` Daniel Borkmann [this message]
2015-10-07 23:20 ` [PATCH net-next v2 2/5] once: make helper generic for calling functions once Daniel Borkmann
2015-10-07 23:52   ` Alexei Starovoitov
2015-10-07 23:20 ` [PATCH net-next v2 3/5] random32: add prandom_seed_full_state helper Daniel Borkmann
2015-10-07 23:54   ` Alexei Starovoitov
2015-10-07 23:20 ` [PATCH net-next v2 4/5] random32: add prandom_init_once helper for own rngs Daniel Borkmann
2015-10-07 23:54   ` Alexei Starovoitov
2015-10-07 23:20 ` [PATCH net-next v2 5/5] bpf: split state from prandom_u32() and consolidate {c,e}BPF prngs Daniel Borkmann
2015-10-08 12:27 ` [PATCH net-next v2 0/5] BPF/random32 updates David Miller

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=5616103B.2030805@iogearbox.net \
    --to=daniel@iogearbox$(echo .)net \
    --cc=ast@plumgrid$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=hannes@stressinduktion$(echo .)org \
    --cc=kbuild-all@01$(echo .)org \
    --cc=lkp@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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