From: Greg KH <greg@kroah.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
bentiss@kernel.org, Jiri Kosina <jikos@kernel.org>
Subject: Re: Patch "HID: bpf: Fix NKRO on Mistel MD770" has been added to the 6.6-stable tree
Date: Thu, 12 Dec 2024 11:59:16 +0100 [thread overview]
Message-ID: <2024121205-wifi-step-8925@gregkh> (raw)
In-Reply-To: <CAO-hwJL7HgrE0wTkG6U47N9k8LRiCR2AqZ4a0CmeX0Lip7uofA@mail.gmail.com>
On Wed, Dec 11, 2024 at 09:27:42AM +0100, Benjamin Tissoires wrote:
> On Tue, Dec 10, 2024 at 10:00 PM Sasha Levin <sashal@kernel.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > HID: bpf: Fix NKRO on Mistel MD770
> >
> > to the 6.6-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-bpf-fix-nkro-on-mistel-md770.patch
> > and it can be found in the queue-6.6 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.
>
>
> Please drop this patch (and in all previous releases).
>
> Again, it makes no sense to backport any files in
> drivers/hid/bpf/progs on kernels before 6.11, and even then, it makes
> very little value as they are also tracked in a different userspace
> project (udev-hid-bpf).
Thanks for the info, now dropped from all queues.
greg k-h
prev parent reply other threads:[~2024-12-12 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241210210012.3586101-1-sashal@kernel.org>
2024-12-11 8:27 ` Patch "HID: bpf: Fix NKRO on Mistel MD770" has been added to the 6.6-stable tree Benjamin Tissoires
2024-12-12 10:59 ` 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=2024121205-wifi-step-8925@gregkh \
--to=greg@kroah.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bentiss@kernel.org \
--cc=jikos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox