All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Kamal Mostafa <kamal.mostafa@canonical.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	tonyb@cybernetics.com, changbin.du@intel.com,
	Alan Stern <stern@rowland.harvard.edu>,
	baolu.lu@linux.intel.com, chasemetzger15@gmail.com,
	kborer@gmail.com, mathias.nyman@linux.intel.com,
	jun.li@freescale.com, Robert.Schlabbach@gmx.net,
	USB list <linux-usb@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH][v3.13.y-ckt][v3.19-ckt][v4.2.y-ckt]Revert "usb: hub: do not clear BOS field during reset device"
Date: Fri, 20 May 2016 11:56:39 -0400	[thread overview]
Message-ID: <573F33B7.5040602@canonical.com> (raw)

Hello,

Please consider including commit 
e5bdfd50d6f76077bf8441d130c606229e100d40 in the next v3.13.y-ckt,
v3.19-ckt and v4.2.y-ckt releases.  It was included upstream as of
v4.5-rc6.  This commit has been tested and resolves the following bug:
http://pad.lv/1582864.

According to the commit message, this patch has already been included in
the following -stable kernels:
    4.5.0-rc4 (current git)
    4.4.2
    4.3.6 (currently in review)
    4.1.18
    3.18.27
    3.14.61


commit e5bdfd50d6f76077bf8441d130c606229e100d40
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Sat Feb 20 14:19:34 2016 -0800

    Revert "usb: hub: do not clear BOS field during reset device"




Sincerely,

Joseph Salisbury

             reply	other threads:[~2016-05-20 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 15:56 Joseph Salisbury [this message]
2016-05-20 21:55 ` [PATCH][v3.13.y-ckt][v3.19-ckt][v4.2.y-ckt]Revert "usb: hub: do not clear BOS field during reset device" Kamal Mostafa

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=573F33B7.5040602@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=Robert.Schlabbach@gmx.net \
    --cc=baolu.lu@linux.intel.com \
    --cc=changbin.du@intel.com \
    --cc=chasemetzger15@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jun.li@freescale.com \
    --cc=kamal.mostafa@canonical.com \
    --cc=kborer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tonyb@cybernetics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.