[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48414031-de4e-a36a-95d7-84c31f1616e4@gmail.com>
Date: Wed, 16 Nov 2016 12:06:17 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: kbuild test robot <lkp@...el.com>,
gregory.clement@...e-electrons.com,
thomas.petazzoni@...e-electrons.com, mw@...ihalf.com
Cc: kbuild-all@...org, netdev@...r.kernel.org, davem@...emloft.net,
mw@...ihalf.com, arnd@...db.de, Shaohui.Xie@...escale.com
Subject: Re: [PATCH net-next v3 3/3] net: marvell: Allow drivers to be built
with COMPILE_TEST
On 11/16/2016 11:04 AM, kbuild test robot wrote:
> Hi Florian,
>
> [auto build test WARNING on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Florian-Fainelli/net-gianfar_ptp-Rename-FS-bit-to-FIPERST/20161116-095805
> config: s390-allyesconfig (attached as .config)
> compiler: s390x-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> 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=s390
>
> All warnings (new ones prefixed by >>):
While we could fix some of these warnings for 64-bit architectures, the
mvneta and mvpp2 drivers would not work there anyway since they assume
physical addresses will always be 32-bit wide and casts such addresses
accordingly.
Should we still silence these warnings?
--
Florian
Powered by blists - more mailing lists