From: Greg KH <gregkh@linuxfoundation.org>
To: Mark O'Donovan <shiftee@posteo.net>
Cc: Sasha Levin <sashal@kernel.org>,
stable-commits@vger.kernel.org, stable@vger.kernel.org,
Hannes Reinecke <hare@suse.de>, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: Patch "nvme-auth: unlock mutex in one place only" has been added to the 6.1-stable tree
Date: Mon, 18 Dec 2023 11:31:48 +0100 [thread overview]
Message-ID: <2023121822-squiggly-septic-d950@gregkh> (raw)
In-Reply-To: <bfe2af35-b057-4335-ade9-8b8cf4d9532b@posteo.net>
On Sat, Dec 16, 2023 at 09:33:50PM +0000, Mark O'Donovan wrote:
> This is wrong. This patch should not be applied to 6.1
But 6.6.y is ok?
Why one and not both?
Actually why is this really needed? I'll drop it from both trees now...
thanks,
greg k-h
prev parent reply other threads:[~2023-12-18 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231216210540.1038298-1-sashal@kernel.org>
2023-12-16 21:33 ` Patch "nvme-auth: unlock mutex in one place only" has been added to the 6.1-stable tree Mark O'Donovan
2023-12-18 10:31 ` 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=2023121822-squiggly-septic-d950@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=sagi@grimberg.me \
--cc=sashal@kernel.org \
--cc=shiftee@posteo.net \
--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