From: Bin Liu <b-liu@ti.com>
To: <gregkh@linuxfoundation.org>
Cc: <gkaiser@google.com>, <stable@vger.kernel.org>,
<stable-commits@vger.kernel.org>
Subject: Re: Patch "[PATCH] Revert "usb: musb: fix tx fifo flush handling again"" has been added to the 3.18-stable tree
Date: Wed, 20 Sep 2017 08:20:13 -0500 [thread overview]
Message-ID: <20170920132013.GA3864@uda0271908> (raw)
In-Reply-To: <15059036547773@kroah.com>
Hi Greg,
On Wed, Sep 20, 2017 at 12:34:14PM +0200, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> [PATCH] Revert "usb: musb: fix tx fifo flush handling again"
>
> to the 3.18-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> revert-usb-musb-fix-tx-fifo-flush-handling-again.patch
> and it can be found in the queue-3.18 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> From 817bdbb406234e405e01790dfc6fffd91a15367e Mon Sep 17 00:00:00 2001
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Wed, 20 Sep 2017 12:31:05 +0200
> Subject: [PATCH] Revert "usb: musb: fix tx fifo flush handling again"
>
> This reverts commit 98b91bfa5e478b9bf332f9f149b1c25ffd58f877 which is
> commit 45d73860530a14c608f410b91c6c341777bfa85d upstream.
>
> It should not have been applied to the 3.18-stable tree at all.
The original commit 45d73860530a14c608f410b91c6c341777bfa85d upstream
does mention it is applicable to v4.4+,
Cc: stable@vger.kernel.org # v4.4+
but it doesn't have 'Fixes ...' line.
What is the best format of a commit message to help to prevent this
incident happen again?
Regards,
-Bin.
next prev parent reply other threads:[~2017-09-20 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 10:34 Patch "[PATCH] Revert "usb: musb: fix tx fifo flush handling again"" has been added to the 3.18-stable tree gregkh
2017-09-20 13:20 ` Bin Liu [this message]
2017-09-20 14:58 ` Greg KH
2017-09-20 19:19 ` Bin Liu
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=20170920132013.GA3864@uda0271908 \
--to=b-liu@ti.com \
--cc=gkaiser@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.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;
as well as URLs for NNTP newsgroup(s).