From: Ralf Baechle <ralf@linux-mips.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: "Steven J. Hill" <Steven.Hill@imgtec.com>,
kbuild-all@01.org, linux-mips@linux-mips.org
Subject: Re: [mips-sjhill:mips-for-linux-next 37/40] arch/mips/cavium-octeon/octeon-usb.c:256:12: error: 'union cvmx_gpio_bit_cfgx' has no member named 'cn73xx'
Date: Thu, 20 Apr 2017 11:29:42 +0200 [thread overview]
Message-ID: <20170420092942.GC28041@linux-mips.org> (raw)
In-Reply-To: <201704191014.yOa9zsIb%fengguang.wu@intel.com>
On Wed, Apr 19, 2017 at 10:51:24AM +0800, kbuild test robot wrote:
> tree: git://git.linux-mips.org/pub/scm/sjhill/linux-sjhill.git mips-for-linux-next
> head: 1f658c055f06e85d017652fd9cf0d1253277a316
> commit: 23c1c950836486c2cc15437e2e800c557fa96f21 [37/40] MIPS: Octeon: Remove unused GPIO types and macros.
> config: mips-cavium_octeon_defconfig (attached as .config)
> compiler: mips64-linux-gnuabi64-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 23c1c950836486c2cc15437e2e800c557fa96f21
> # save the attached .config to linux build tree
> make.cross ARCH=mips
>
> All errors (new ones prefixed by >>):
>
> arch/mips/cavium-octeon/octeon-usb.c: In function 'dwc3_octeon_config_power':
> >> arch/mips/cavium-octeon/octeon-usb.c:256:12: error: 'union cvmx_gpio_bit_cfgx' has no member named 'cn73xx'
> gpio_bit.cn73xx.output_sel = (index == 0 ? 0x14 : 0x15);
> ^
> >> arch/mips/cavium-octeon/octeon-usb.c:261:12: error: 'union cvmx_gpio_bit_cfgx' has no member named 'cn70xx'
> gpio_bit.cn70xx.output_sel = (index == 0 ? 0x14 : 0x19);
> ^
> >> arch/mips/cavium-octeon/octeon-usb.c:264:33: error: implicit declaration of function 'CVMX_GPIO_XBIT_CFGX' [-Werror=implicit-function-declaration]
> gpio_bit.u64 = cvmx_read_csr(CVMX_GPIO_XBIT_CFGX(gpio));
> ^~~~~~~~~~~~~~~~~~~
> arch/mips/cavium-octeon/octeon-usb.c:266:12: error: 'union cvmx_gpio_bit_cfgx' has no member named 'cn70xx'
> gpio_bit.cn70xx.output_sel = (index == 0 ? 0x14 : 0x19);
> ^
> cc1: all warnings being treated as errors
I've dropped the offending commit 23c1c9508364 ("MIPS: Octeon: Remove
unused GPIO types and macros.") and the following commit 8ed898353e36
("MIPS: Octeon: Remove unused MIO types and macros.") which was causing
CC drivers/net/ethernet/cavium/octeon/octeon_mgmt.o
drivers/net/ethernet/cavium/octeon/octeon_mgmt.c: In function ‘octeon_mgmt_ioctl_hwtstamp’:
drivers/net/ethernet/cavium/octeon/octeon_mgmt.c:707:20: error: ‘CVMX_MIO_PTP_CLOCK_COMP’ undeclared (first use in this function)
cvmx_write_csr(CVMX_MIO_PTP_CLOCK_COMP, clock_comp);
^
drivers/net/ethernet/cavium/octeon/octeon_mgmt.c:707:20: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:294: recipe for target 'drivers/net/ethernet/cavium/octeon/octeon_mgmt.o' failed
make[5]: *** [drivers/net/ethernet/cavium/octeon/octeon_mgmt.o] Error 1
Ralf
prev parent reply other threads:[~2017-04-20 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 2:51 [mips-sjhill:mips-for-linux-next 37/40] arch/mips/cavium-octeon/octeon-usb.c:256:12: error: 'union cvmx_gpio_bit_cfgx' has no member named 'cn73xx' kbuild test robot
2017-04-20 9:29 ` Ralf Baechle [this message]
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=20170420092942.GC28041@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Steven.Hill@imgtec.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--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