From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:60301 "EHLO
	mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751082AbcDIA6Q (ORCPT
	<rfc822;stable@vger.kernel.org>); Fri, 8 Apr 2016 20:58:16 -0400
Date: Fri, 8 Apr 2016 17:58:14 -0700
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
Message-ID: <20160409005814.GA27479@kroah.com>
References: <57083C8C.8000804@synopsys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <57083C8C.8000804@synopsys.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

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