From: Greg KH <gregkh@linuxfoundation.org>
To: Saranya Gopal <saranya.gopal@intel.com>
Cc: stable@vger.kernel.org, linux-usb@vger.kernel.org,
fei.yang@intel.com, john.stultz@linaro.org,
Felipe Balbi <felipe.balbi@linux.intel.com>
Subject: Re: [PATCH 4.19.y 3/3] usb: dwc3: gadget: remove req->started flag
Date: Mon, 29 Jul 2019 18:56:11 +0200 [thread overview]
Message-ID: <20190729165611.GA14160@kroah.com> (raw)
In-Reply-To: <1564407819-10746-4-git-send-email-saranya.gopal@intel.com>
On Mon, Jul 29, 2019 at 07:13:39PM +0530, Saranya Gopal wrote:
> From: Felipe Balbi <felipe.balbi@linux.intel.com>
>
> [Upstream commit 7c3d7dc89e57a1d43acea935882dd8713c9e639f]
>
> Now that we have req->status, we don't need this extra flag
> anymore. It's safe to remove it.
>
> Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
> Signed-off-by: Saranya Gopal <saranya.gopal@intel.com>
> ---
> drivers/usb/dwc3/core.h | 2 --
> drivers/usb/dwc3/gadget.c | 1 -
> drivers/usb/dwc3/gadget.h | 2 --
> 3 files changed, 5 deletions(-)
Why is this patch needed for a stable tree? It just cleans stuff up, it
doesn't actually change any functionality.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-29 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 13:43 [PATCH 4.19.y 0/3] usb: dwc3: Prevent requests from being queued twice Saranya Gopal
2019-07-29 13:43 ` [PATCH 4.19.y 1/3] usb: dwc3: gadget: add dwc3_request status tracking Saranya Gopal
2019-07-29 13:43 ` [PATCH 4.19.y 2/3] usb: dwc3: gadget: prevent dwc3_request from being queued twice Saranya Gopal
2019-07-29 16:56 ` Greg KH
2019-07-29 17:06 ` Gopal, Saranya
2019-07-29 17:28 ` Greg KH
2019-07-29 13:43 ` [PATCH 4.19.y 3/3] usb: dwc3: gadget: remove req->started flag Saranya Gopal
2019-07-29 16:56 ` Greg KH [this message]
2019-07-29 16:59 ` Gopal, Saranya
2019-07-29 17:34 ` [PATCH 4.19.y 0/3] usb: dwc3: Prevent requests from being queued twice Greg KH
2019-07-30 9:29 ` Gopal, Saranya
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=20190729165611.GA14160@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fei.yang@intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=linux-usb@vger.kernel.org \
--cc=saranya.gopal@intel.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 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.