From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
will@kernel.org
Subject: Re: [PATCH] arm64: ftrace: add missing BTIs
Date: Fri, 3 Dec 2021 11:50:44 +0000 [thread overview]
Message-ID: <YaoElBiJbVdCqoia@FVFF77S0Q05N> (raw)
In-Reply-To: <Yai9PevQnyPkBnsi@sirena.org.uk>
On Thu, Dec 02, 2021 at 12:34:05PM +0000, Mark Brown wrote:
> On Thu, Dec 02, 2021 at 10:43:39AM +0000, Mark Rutland wrote:
> > On Mon, Nov 29, 2021 at 05:48:46PM +0000, Mark Brown wrote:
>
> > > The unconditional definition seems like it might be neater as a
> > > minimally intrusive thing for backporting, we can always refactor later.
>
> > The problem with that is that for consistency we should remove the ifdeferry
> > from the kasan trampoline at the same time, which either means an unnecessary
> > dependency as above, or splitting this into three patches, one of which should
> > not be backported.
>
> Or just two, this one and a cleanup.
Sure, a follow-up cleanup is fine, but critically the cleanup need not be
backported, which is why I said:
| I completely agree the ifdeferry is ugly, and I do intend to follow up on
| that regardless. If you feel strongly that we should get rid of that now, I
| can spin a v2 with a second patch to clean that up; otherwise I'll do that as
| part of a later series.
Since Will has taken this patch as-is, and the fixes for v5.16-rc4 have already
been tagged, I'll follow up with cleanup once that's merged to avoid being
based on an ephemeral branch.
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-03 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 13:57 [PATCH] arm64: ftrace: add missing BTIs Mark Rutland
2021-11-29 16:50 ` Mark Brown
2021-11-29 17:37 ` Mark Rutland
2021-11-29 17:48 ` Mark Brown
2021-12-02 10:43 ` Mark Rutland
2021-12-02 12:34 ` Mark Brown
2021-12-03 11:50 ` Mark Rutland [this message]
2021-12-03 13:29 ` Mark Brown
2021-12-02 10:59 ` Will Deacon
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=YaoElBiJbVdCqoia@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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