From: svenkatr@ti.com (Venkatraman S)
To: linux-arm-kernel@lists.infradead.org
Subject: configuration warnings with omap_3630sdp_defconfig in 2.6.35-rc5
Date: Tue, 20 Jul 2010 15:52:08 +0530 [thread overview]
Message-ID: <AANLkTimh0MBzANu1rmLb7q1tYQMywznQd5DJ_mUKp_cZ@mail.gmail.com> (raw)
While trying to build omap_3630sdp_defconfig on Linus's 2.6.35-rc5, I
get these warnings..
I understand these could be related to the recent defconfig changes.
I will try to investigate; posted here to know if anyone has found a
fix already..
------------------------------
scripts/kconfig/conf -s arch/arm/Kconfig
can't copy type 0
warning: (USB_MUSB_HDRC_HCD && USB_SUPPORT && USB_MUSB_HDRC &&
(USB_MUSB_HOST || USB_MUSB_OTG) && USB_GADGET_MUSB_HDRC ||
USB_MUSB_OTG && <choice> && USB && USB_GADGET && PM && EXPERIMENTAL)
selects USB_OTG which has unmet direct dependencies (USB_GADGET_OMAP
&& ARCH_OMAP_OTG && USB_OHCI_HCD)
warning: (USB_MUSB_HDRC_HCD && USB_SUPPORT && USB_MUSB_HDRC &&
(USB_MUSB_HOST || USB_MUSB_OTG) && USB_GADGET_MUSB_HDRC ||
USB_MUSB_OTG && <choice> && USB && USB_GADGET && PM && EXPERIMENTAL)
selects USB_OTG which has unmet direct dependencies (USB_GADGET_OMAP
&& ARCH_OMAP_OTG && USB_OHCI_HCD)
------------------------------
Regards,
Venkat.
reply other threads:[~2010-07-20 10:22 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=AANLkTimh0MBzANu1rmLb7q1tYQMywznQd5DJ_mUKp_cZ@mail.gmail.com \
--to=svenkatr@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).