Linux RAID subsystem development
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Shaohua Li <shli@fb.com>
Cc: kbuild-all@01.org, NeilBrown <neilb@suse.com>,
	linux-raid@vger.kernel.org
Subject: [md:devel 18/33] mips-linux-gnu-ld: drivers/md/raid5-cache.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
Date: Fri, 2 Oct 2015 22:04:00 +0800	[thread overview]
Message-ID: <201510022259.XqjotbWf%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

tree:   git://neil.brown.name/md devel
head:   c09760178dc0824490edc6ac4664dbce3c34d002
commit: c014ca45166e12c74dd0809911f36ffdb8224450 [18/33] raid5: add basic stripe log
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
        git checkout c014ca45166e12c74dd0809911f36ffdb8224450
        # save the attached .config to linux build tree
        make.cross ARCH=mips 

All warnings (new ones prefixed by >>):

   mips-linux-gnu-ld: drivers/md/raid5.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
   mips-linux-gnu-ld: drivers/md/raid5.o: warning: Inconsistent ISA extensions between e_flags and .MIPS.abiflags
>> mips-linux-gnu-ld: drivers/md/raid5-cache.o: warning: Inconsistent ISA between e_flags and .MIPS.abiflags
>> mips-linux-gnu-ld: drivers/md/raid5-cache.o: warning: Inconsistent ISA extensions between e_flags and .MIPS.abiflags

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 14106 bytes --]

                 reply	other threads:[~2015-10-02 14:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201510022259.XqjotbWf%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=shli@fb.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