From: Bin Liu <b-liu@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: kbuild test robot <fengguang.wu@intel.com>, <kbuild-all@01.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: drivers/usb/musb/tusb6010.c:142:21: error: 'USB_INDEX' undeclared
Date: Thu, 8 Sep 2016 13:26:32 -0500 [thread overview]
Message-ID: <20160908182609.GG4054@uda0271908> (raw)
In-Reply-To: <20160908174521.fcrjbcwktfiuujib@atomide.com>
Hi Tony,
On Thu, Sep 08, 2016 at 10:45:21AM -0700, Tony Lindgren wrote:
> Hi,
>
> Adding Bin to Cc.
>
> * kbuild test robot <fengguang.wu@intel.com> [160611 13:27]:
> > Hi,
> >
> > FYI, the error/warning still remains.
>
> Sorry just noticed this going through my inbox.. Please let me know
> if there are other pending build errors I may have missed.
>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 45b00c94be33db5d00595046663163ce55cbbfb9
> > commit: d026e9c76aac3632af174cf02d5c94defa5e6026 usb: musb: Change end point selection to use new IO access
> > date: 1 year, 7 months ago
> > config: blackfin-allmodconfig (attached as .config)
> > compiler: bfin-uclinux-gcc (GCC) 4.6.3
> > 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 d026e9c76aac3632af174cf02d5c94defa5e6026
> > # save the attached .config to linux build tree
> > make.cross ARCH=blackfin
> >
> > All errors (new ones prefixed by >>):
> >
> > drivers/usb/musb/tusb6010.c: In function 'tusb_get_revision':
> > drivers/usb/musb/tusb6010.c:53:26: error: 'TUSB_DMA_CTRL_REV' undeclared (first use in this function)
>
> The patch below should fix this, I don't have any blackfin
> machines or compilers here to test with though.
>
> Regards,
>
> Tony
>
> 8< ---------------------
> From: Tony Lindgren <tony@atomide.com>
> Date: Thu, 8 Sep 2016 10:36:47 -0700
> Subject: [PATCH] usb: musb: Fix tusb6010 compile error on blackfin
>
> We have CONFIG_BLACKFIN ifdef redefining all musb registers in
> musb_regs.h and tusb6010.h is never included causing a build
> error with blackfin-allmodconfig and COMPILE_TEST.
>
> Let's fix the issue by not building tusb6010 if CONFIG_BLACKFIN
> is selected.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
> --- a/drivers/usb/musb/Kconfig
> +++ b/drivers/usb/musb/Kconfig
> @@ -87,7 +87,7 @@ config USB_MUSB_DA8XX
> config USB_MUSB_TUSB6010
> tristate "TUSB6010"
> depends on HAS_IOMEM
> - depends on ARCH_OMAP2PLUS || COMPILE_TEST
> + depends on (ARCH_OMAP2PLUS || COMPILE_TEST) && !BLACKFIN
Would this cause more issue later when trying to enable all glue drivers
in one build?
The macros defined in tusb6010.h are only used in tusb6010.c, so how
about move '#include "tusb6010.h"' from musb_regs.h to tusb6010.c
instead? This gives flexibility to random config test, isn't it?
Regards,
-Bin.
next prev parent reply other threads:[~2016-09-08 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 20:10 drivers/usb/musb/tusb6010.c:142:21: error: 'USB_INDEX' undeclared kbuild test robot
2016-09-08 17:45 ` Tony Lindgren
2016-09-08 18:26 ` Bin Liu [this message]
2016-09-13 22:35 ` Tony Lindgren
2016-09-14 13:13 ` Bin Liu
2016-09-14 14:35 ` Tony Lindgren
2016-09-14 13:37 ` Bin Liu
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=20160908182609.GG4054@uda0271908 \
--to=b-liu@ti.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).