From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"balbi@kernel.org" <balbi@kernel.org>
Cc: "romain.izard.pro@gmail.com" <romain.izard.pro@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"ruslan.bilovol@gmail.com" <ruslan.bilovol@gmail.com>,
"hare@suse.com" <hare@suse.com>,
"cascardo@cascardo.eti.br" <cascardo@cascardo.eti.br>
Subject: Re: [PATCH 1/2] usb: gadget: restore tristate-choice for legacy gadgets
Date: Mon, 11 Dec 2017 16:09:20 +0000 [thread overview]
Message-ID: <1513008559.2747.0.camel@wdc.com> (raw)
In-Reply-To: <20171211113048.3514863-1-arnd@arndb.de>
On Mon, 2017-12-11 at 12:30 +0100, Arnd Bergmann wrote:
> One patch that was meant as a cleanup apparently did more than it intended,
> allowing all combinations of legacy gadget drivers to be built into the
> kernel, and leaving an empty 'choice' statement behind:
>
> drivers/usb/gadget/Kconfig:487:warning: choice default symbol 'USB_ETH' is not contained in the choice
>
> The description of commit 7a9618a22aad ("usb: gadget: allow to enable legacy
> drivers without USB_ETH") was a bit cryptic, as it did not change the
> behavior of USB_ETH other than allowing it to be built into the kernel
> alongside other legacy gadgets, which is not a valid configuration.
>
> As Felipe explained in the description for commit bc49d1d17dcf ("usb:
> gadget: don't couple configfs to legacy gadgets"), the configfs based
> gadgets can be freely configured as loadable modules or built-in
> drivers, but the legacy gadgets can only be modules if there is more
> than one of them, so we require the 'choice' statement here.
>
> This leaves the added USB_GADGET_LEGACY menuconfig symbol in place,
> but then restores the 'choice' below it, so we can enforce the
> single-legacy-gadget rule as before.
Hello Arnd,
A discussion is ongoing about whether or not commit 7a9618a22aad should be reverted.
Please drop this patch until a conclusion has been reached.
Thanks,
Bart.
next prev parent reply other threads:[~2017-12-11 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 11:30 [PATCH 1/2] usb: gadget: restore tristate-choice for legacy gadgets Arnd Bergmann
2017-12-11 11:30 ` [PATCH 2/2] usb: gadget: webcam: fix V4L2 Kconfig dependency Arnd Bergmann
2017-12-11 16:09 ` Bart Van Assche [this message]
2017-12-11 16:27 ` [PATCH 1/2] usb: gadget: restore tristate-choice for legacy gadgets Arnd Bergmann
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=1513008559.2747.0.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=arnd@arndb.de \
--cc=balbi@kernel.org \
--cc=cascardo@cascardo.eti.br \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=romain.izard.pro@gmail.com \
--cc=ruslan.bilovol@gmail.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