From: Greg KH <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: Patch "arm64: fpsimd: Bring cond_yield asm macro in line with new rules" has been added to the 6.6-stable tree
Date: Thu, 6 Jun 2024 15:13:16 +0200 [thread overview]
Message-ID: <2024060653-enlarging-imprecise-2831@gregkh> (raw)
In-Reply-To: <CAMj1kXHrpZzJvvi+4RaMVV5_tsEU62_EC-7MboHBbR1hTMgTcg@mail.gmail.com>
On Thu, Jun 06, 2024 at 02:42:09PM +0200, Ard Biesheuvel wrote:
> On Thu, 6 Jun 2024 at 01:11, Sasha Levin <sashal@kernel.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > arm64: fpsimd: Bring cond_yield asm macro in line with new rules
> >
> > 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:
> > arm64-fpsimd-bring-cond_yield-asm-macro-in-line-with.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.
> >
>
> NAK
>
> None of these changes belong in v6.6 - please drop all of them.
Odd, yeah, we add some stuff, then the patch, and then the revert of it,
but not then these. I'll go drop them all, thanks for the review!
greg k-h
next prev parent reply other threads:[~2024-06-06 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240605231152.3112791-1-sashal@kernel.org>
2024-06-06 12:42 ` Patch "arm64: fpsimd: Bring cond_yield asm macro in line with new rules" has been added to the 6.6-stable tree Ard Biesheuvel
2024-06-06 13:13 ` Greg KH [this message]
2024-06-06 13:14 ` Greg KH
2024-06-06 13:16 ` Ard Biesheuvel
2024-06-06 14:07 ` Greg KH
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=2024060653-enlarging-imprecise-2831@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=will@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