From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: John Youn <John.Youn@synopsys.com>
Cc: stable@vger.kernel.org, Felipe Balbi <balbi@kernel.org>
Subject: Re: usb: gadget: composite: Return bcdUSB 0x0310
Date: Fri, 8 Apr 2016 17:58:14 -0700 [thread overview]
Message-ID: <20160409005814.GA27479@kroah.com> (raw)
In-Reply-To: <57083C8C.8000804@synopsys.com>
On Fri, Apr 08, 2016 at 04:19:40PM -0700, John Youn wrote:
> Hi,
>
> I'd like to request the following be applied to stable trees 3.2+.
>
> 1a85329171094951956a37acc8abb7e51c1e742e ("usb: gadget: composite:
> Return bcdUSB 0x0310")
>
> The USB 3.1 specification replaces the USB 3.0 specification and all new
> devices that are running at SuperSpeed or higher speeds must report a
> bcdUSB of 0x0310.
That doesn't seem very "backwards compatible" of the spec to me, what
happens if you return a 3.0 string, when you really are only handling
3.0 things like we do in older kernels?
thanks,
greg k-h
next prev parent reply other threads:[~2016-04-09 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 23:19 usb: gadget: composite: Return bcdUSB 0x0310 John Youn
2016-04-09 0:58 ` Greg Kroah-Hartman [this message]
2016-04-11 21:28 ` John Youn
2016-04-11 22:11 ` Greg Kroah-Hartman
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=20160409005814.GA27479@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=John.Youn@synopsys.com \
--cc=balbi@kernel.org \
--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