From: Sasha Levin <sashal@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Fangrui Song <maskray@google.com>,
Ard Biesheuvel <ardb@kernel.org>, Will Deacon <will@kernel.org>,
peterz@infradead.org, jpoimboe@kernel.org, jbaron@akamai.com,
catalin.marinas@arm.com, nathan@kernel.org,
linux-arm-kernel@lists.infradead.org, llvm@lists.linux.dev
Subject: Re: [PATCH AUTOSEL 6.7 07/26] arm64: jump_label: use constraints "Si" instead of "i"
Date: Mon, 18 Mar 2024 09:24:02 -0400 [thread overview]
Message-ID: <ZfhAcikh8h9D7crJ@sashalap> (raw)
In-Reply-To: <ZeCpOPDi18OBEclz@FVFF77S0Q05N>
On Thu, Feb 29, 2024 at 03:56:40PM +0000, Mark Rutland wrote:
>On Thu, Feb 29, 2024 at 10:48:26AM -0500, Sasha Levin wrote:
>> From: Fangrui Song <maskray@google.com>
>>
>> [ Upstream commit f9daab0ad01cf9d165dbbbf106ca4e61d06e7fe8 ]
>
>That upstream patch caused issues and was subsequently reverted in commit:
>
> a6b3eb304a82c29665a0ab947cfe276f6d29f523
> ("Revert "arm64: jump_label: use constraints "Si" instead of "i""")
>
>Please drop this; it'll break stable in the same way, and it wasn't necessary
>to backport in the first place.
Will do.
>As an aside, that revert has been upstream since v6.8-rc4, ~2.5 weeks ago; it's
>unfortunate for the broken patch to be AUTOSEL'd now! It'd be good if something
>could automatically check for reverts in mainline...
Sorry for the noise - usually the fixes/revert check happens before
commits actually end up in the queue.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-03-18 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229154851.2849367-1-sashal@kernel.org>
2024-02-29 15:48 ` [PATCH AUTOSEL 6.7 07/26] arm64: jump_label: use constraints "Si" instead of "i" Sasha Levin
2024-02-29 15:56 ` Mark Rutland
2024-03-18 13:24 ` Sasha Levin [this message]
2024-02-29 15:48 ` [PATCH AUTOSEL 6.7 25/26] gen_compile_commands: fix invalid escape sequence warning Sasha Levin
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=ZfhAcikh8h9D7crJ@sashalap \
--to=sashal@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=maskray@google.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.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