From: Arnd Bergmann <arnd@arndb.de>
To: Peter Chen <hzpeterchen@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Chen <peter.chen@nxp.com>, Felipe Balbi <balbi@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: Kconfig: make USB_ULPI_BUS select USB_COMMON
Date: Tue, 13 Sep 2016 12:32:54 +0200 [thread overview]
Message-ID: <3708710.f6PqhfJbOg@wuerfel> (raw)
In-Reply-To: <20160913085005.GA30760@b29397-desktop>
On Tuesday, September 13, 2016 4:50:05 PM CEST Peter Chen wrote:
> On Tue, Sep 13, 2016 at 09:36:39AM +0200, Arnd Bergmann wrote:
> > On Tuesday, September 13, 2016 3:19:42 PM CEST Peter Chen wrote:
> > >
> > > I just see below Kconfig entry at the same Kconfig
> > > (drivers/usb/Kconfig), and forget your changes.
> > >
> > > config USB_LED_TRIG
> > > bool "USB LED Triggers"
> > > depends on LEDS_CLASS && USB_COMMON && LEDS_TRIGGERS
> > > help
> > > This option adds LED triggers for USB host and/or gadget activity.
> > >
> > > Say Y here if you are working on a system with led-class supported
> > > LEDs and you want to use them as activity indicators for USB host or
> > > gadget.
> > >
> > > Just grep it, some Kconfig still uses depends on for USB_COMMON, let me
> > > change it together.
> > >
> >
> > I suspect this one above should instead depend on "USB_SUPPORT".
> >
>
> No, it is embraced by "if USB_SUPPORT", so we don't need to add it
> additionally.
Right, makes sense.
> Even USB_SUPPORT is chosen, the USB_COMMON may still
> not be chosen, so we need let USB_LET_TRIG select USB_COMMON
> explicitly.
My thought was that all users that could possibly call the
USB_LED_TRIG interfaces already rely on USB_COMMON to
be present.
There is probably no real downside in having the 'select USB_COMMON',
but it shouldn't actually be needed. It would be somewhat unusual
though to enable USB_LED_TRIG and not build the file because
we don't enter the directory, so maybe it's better to have it after
all.
Arnd
prev parent reply other threads:[~2016-09-13 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 15:36 Arnd Bergmann
2016-09-13 1:48 ` Peter Chen
2016-09-13 7:04 ` Arnd Bergmann
2016-09-13 7:19 ` Peter Chen
2016-09-13 7:36 ` Arnd Bergmann
2016-09-13 8:50 ` Peter Chen
2016-09-13 10:32 ` Arnd Bergmann [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=3708710.f6PqhfJbOg@wuerfel \
--to=arnd@arndb.de \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hzpeterchen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.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
all inboxes | Powered by JetHome®