From: Bjorn Helgaas <helgaas@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-pci@vger.kernel.org,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [linux-next:master 12786/13335] aarch64-linux-objdump: warning: drivers/pci/pcie/edr.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
Date: Wed, 1 Apr 2020 10:21:57 -0500 [thread overview]
Message-ID: <20200401152157.GA60873@google.com> (raw)
In-Reply-To: <202004012149.oJg30gzP%lkp@intel.com>
[+cc Sathy, Catalin, linux-pci]
On Wed, Apr 01, 2020 at 09:56:53PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 3eb7cccdb3ae41ebb6a2f5f1ccd2821550c61fe1
> commit: 91db57acf85cc283cea7ed5d198e7f2e0c013d1e [12786/13335] Merge remote-tracking branch 'pci/next'
> config: arm64-allyesconfig (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 91db57acf85cc283cea7ed5d198e7f2e0c013d1e
> # save the attached .config to linux build tree
> GCC_VERSION=9.3.0 make.cross ARCH=arm64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> aarch64-linux-objdump: warning: drivers/pci/pcie/edr.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
I don't think this is an issue with edr.c. I suspect this is the
toolchain issue mentioned here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2020-April/721695.html
I suspect this may crop up again. I'm assuming I don't need to do
anything about this. Let me know if otherwise.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 12786/13335] aarch64-linux-objdump: warning: drivers/pci/pcie/edr.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
Date: Wed, 01 Apr 2020 10:21:57 -0500 [thread overview]
Message-ID: <20200401152157.GA60873@google.com> (raw)
In-Reply-To: <202004012149.oJg30gzP%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
[+cc Sathy, Catalin, linux-pci]
On Wed, Apr 01, 2020 at 09:56:53PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 3eb7cccdb3ae41ebb6a2f5f1ccd2821550c61fe1
> commit: 91db57acf85cc283cea7ed5d198e7f2e0c013d1e [12786/13335] Merge remote-tracking branch 'pci/next'
> config: arm64-allyesconfig (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 91db57acf85cc283cea7ed5d198e7f2e0c013d1e
> # save the attached .config to linux build tree
> GCC_VERSION=9.3.0 make.cross ARCH=arm64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> aarch64-linux-objdump: warning: drivers/pci/pcie/edr.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000
I don't think this is an issue with edr.c. I suspect this is the
toolchain issue mentioned here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2020-April/721695.html
I suspect this may crop up again. I'm assuming I don't need to do
anything about this. Let me know if otherwise.
Bjorn
next prev parent reply other threads:[~2020-04-01 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 13:56 [linux-next:master 12786/13335] aarch64-linux-objdump: warning: drivers/pci/pcie/edr.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000 kbuild test robot
2020-04-01 15:21 ` Bjorn Helgaas [this message]
2020-04-01 15:21 ` Bjorn Helgaas
2020-04-01 15:35 ` Bjorn Helgaas
2020-04-01 15:35 ` Bjorn Helgaas
2020-04-02 0:17 ` [kbuild-all] " Rong Chen
2020-04-02 0:17 ` Rong Chen
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=20200401152157.GA60873@google.com \
--to=helgaas@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.