From: Greg KH <gregkh@linuxfoundation.org>
To: torvalds@linux-foundation.org
Cc: stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] Linux 5.18" was seriously submitted to be applied to the 1731160ff7c7bbb11bb1aacb14dd25e18d522779-stable tree?
Date: Fri, 3 Jun 2022 18:10:17 +0200 [thread overview]
Message-ID: <YpoyaXzBN61Y2pDf@kroah.com> (raw)
In-Reply-To: <1654271756154144@kroah.com>
On Fri, Jun 03, 2022 at 05:55:56PM +0200, gregkh@linuxfoundation.org wrote:
> The patch below was submitted to be applied to the 1731160ff7c7bbb11bb1aacb14dd25e18d522779-stable tree.
>
> I fail to see how this patch meets the stable kernel rules as found at
> Documentation/process/stable-kernel-rules.rst.
>
> I could be totally wrong, and if so, please respond to
> <stable@vger.kernel.org> and let me know why this patch should be
> applied. Otherwise, it is now dropped from my patch queues, never to be
> seen again.
Ick, sorry, fat-fingered the script, this was wrong, obviously...
prev parent reply other threads:[~2022-06-03 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 15:55 WTF: patch "[PATCH] Linux 5.18" was seriously submitted to be applied to the 1731160ff7c7bbb11bb1aacb14dd25e18d522779-stable tree? gregkh
2022-06-03 16:10 ` 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=YpoyaXzBN61Y2pDf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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