From: Greg KH <greg@kroah.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Sasha Levin <sashal@kernel.org>, "3.8+" <stable@vger.kernel.org>,
stable-commits@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
Jiri Kosina <jikos@kernel.org>
Subject: Re: Patch "HID: playstation: require multicolor LED functionality" has been added to the 5.15-stable tree
Date: Tue, 23 Nov 2021 12:03:08 +0100 [thread overview]
Message-ID: <YZzKbKseHT5xoxSj@kroah.com> (raw)
In-Reply-To: <CAO-hwJLkmZPj25O49Xr++jWcoBUEJHQAtPZFkXTjwFZvRqFKJA@mail.gmail.com>
On Tue, Nov 23, 2021 at 11:59:25AM +0100, Benjamin Tissoires wrote:
> On Mon, Nov 22, 2021 at 12:04 AM Sasha Levin <sashal@kernel.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > HID: playstation: require multicolor LED functionality
> >
> > to the 5.15-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:
> > hid-playstation-require-multicolor-led-functionality.patch
> > and it can be found in the queue-5.15 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.
>
> I am deeply puzzled by this cherry-pick.
>
> The purpose of this patch was to fix fc97b4d6a1a6 ("HID: playstation:
> expose DualSense lightbar through a multi-color LED.")
>
> So unless this patch gets backported in stable (and this is *not* a
> request to do so), bringing in this patch in 5.15 is wrong.
You are right, thanks for catching this, I'll go drop this commit now.
greg k-h
prev parent reply other threads:[~2021-11-23 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211121230439.76777-1-sashal@kernel.org>
2021-11-23 10:59 ` Patch "HID: playstation: require multicolor LED functionality" has been added to the 5.15-stable tree Benjamin Tissoires
2021-11-23 11:03 ` Greg KH [this message]
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=YZzKbKseHT5xoxSj@kroah.com \
--to=greg@kroah.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=jkosina@suse.cz \
--cc=sashal@kernel.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 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.