public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Romain Izard <romain.izard.pro@gmail.com>
Cc: linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"# 4 . 9+" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] usb: gadget: legacy gadgets are optional
Date: Fri, 10 Mar 2017 13:47:52 +0200	[thread overview]
Message-ID: <87fuilxsif.fsf@linux.intel.com> (raw)
In-Reply-To: <CAGkQfmMPRNs7wHA9Wp0EC6gV=Zh_oRXwEyuJ2jdHvO16Pv1owA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]


Hi,

Romain Izard <romain.izard.pro@gmail.com> writes:
> Hello Felipe,
>
> 2017-03-10 10:15 GMT+01:00 Felipe Balbi <balbi@kernel.org>:
>>
>> Hi,
>>
>> Romain Izard <romain.izard.pro@gmail.com> writes:
>>> With commit "usb: gadget: don't couple configfs to legacy gadgets"
>>> it is possible to build a modular kernel with both built-in configfs
>>> support and modular legacy gadget drivers.
>>>
>>> But when building a kernel without modules, it is also necessary to be
>>> able to build with configfs but without any legacy gadget driver.
>>>
>>> Mark the choice for legacy gadget drivers as optional.
>>>
>>> Fixes: bc49d1d17dcf ("usb: gadget: don't couple configfs to legacy gadgets")
>>> Cc: <stable@vger.kernel.org> # 4.9+
>>
>> this is *NOT* a fix since this requirement didn't exist before.
>
> It worked in 4.1, as a non-modular kernel would only have a single entry
> from the USB gadget driver choice option, and USB_CONFIGFS was one of
> those.

but it wasn't a requirement :-)

> When I moved on to 4.9, this configuration could not be selected anymore.

you could've let us know you needed that working :-) That changed quite
a while back :-) Anyway, I get what you mean. I'll take patch for v4.12
with the stable tag in it.

>>> @@ -476,6 +477,12 @@ choice
>>>         not be able work with that controller, or might need to implement
>>>         a less common variant of a device class protocol.
>>>
>>> +       The available choices each represent a single precomposed USB
>>> +       gadget configuration. In the device model, each option contains
>>> +       both the device instanciation as a child for a USB gadget
>>> +       controller, and the relevant drivers for each function declared
>>> +       by the device.
>>
>> unrelated change
>
> I'll split this.

thank you

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-03-10 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 14:10 [PATCH v2] usb: gadget: legacy gadgets are optional Romain Izard
2017-03-10  9:15 ` Felipe Balbi
2017-03-10  9:39   ` Romain Izard
2017-03-10 11:47     ` Felipe Balbi [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=87fuilxsif.fsf@linux.intel.com \
    --to=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=romain.izard.pro@gmail.com \
    --cc=stable@vger.kernel.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