From: Will Deacon <will@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
acme@redhat.com, ardb@kernel.org, bp@alien8.de,
broonie@kernel.org, dave.hansen@linux.intel.com,
joey.gouly@arm.com, jpoimboe@redhat.com, jslaby@suse.cz,
linux-arm-kernel@lists.infradead.org, mingo@redhat.com,
tglx@linutronix.de
Subject: Re: [PATCH v4 0/4] linkage: better symbol aliasing
Date: Tue, 22 Feb 2022 22:40:57 +0000 [thread overview]
Message-ID: <20220222224056.GA16976@willie-the-truck> (raw)
In-Reply-To: <20220222100918.GA16108@willie-the-truck>
On Tue, Feb 22, 2022 at 10:09:19AM +0000, Will Deacon wrote:
> Hi Peter,
>
> On Thu, Feb 17, 2022 at 11:58:31AM +0100, Peter Zijlstra wrote:
> > On Wed, Feb 16, 2022 at 04:22:25PM +0000, Mark Rutland wrote:
> > > Catalin, Will, Peter: I think this is ready now and would like to get it
> > > queued, but it looks like this may (trivially) conflict with other bits
> > > we'll want to queue in either the arm64 tree (Joey's string routine
> > > changes [4]), or tip tree (Peter's IBT series).
> > >
> > > I assume the best thing to do would be to have a stable branch merged in
> > > both of those. I've tagged this such that it can be pulled (details
> > > below); Peter also suggested he could make a stable branch in the tip
> > > tree. Any preference?
> >
> > No real preference, The conflicts on my end are really rather trivial
> > IIRC, but they're a nice clean-up.
> >
> > If I don't take then, feel free to add:
> >
> > Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> Mark mentioned yesterday that this series will conflict with some pending
> rework to the arm64 string routines [1], so we probably want a shared
> branch to handle the fallout.
>
> Do you plan to queue this someplace in -tip that I can pull from, or
> shall I create a stable branch on the arm64 side?
Following discussion on IRC, I've pushed this out to the for-next/linkage
branch on the arm64 git. Let's give it a day or so in -next, then if it
doesn't fall apart you can pull it in to -tip as well.
Cheers,
Will
_______________________________________________
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:[~2022-02-22 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:22 [PATCH v4 0/4] linkage: better symbol aliasing Mark Rutland
2022-02-16 16:22 ` [PATCH v4 1/4] linkage: add SYM_FUNC_ALIAS{,_LOCAL,_WEAK}() Mark Rutland
2022-02-16 16:22 ` [PATCH v4 2/4] arm64: clean up symbol aliasing Mark Rutland
2022-02-16 16:22 ` [PATCH v4 3/4] x86: " Mark Rutland
2022-02-16 16:22 ` [PATCH v4 4/4] linkage: remove SYM_FUNC_{START,END}_ALIAS() Mark Rutland
2022-02-17 10:58 ` [PATCH v4 0/4] linkage: better symbol aliasing Peter Zijlstra
2022-02-22 10:09 ` Will Deacon
2022-02-22 22:40 ` Will Deacon [this message]
2022-02-22 22:38 ` 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=20220222224056.GA16976@willie-the-truck \
--to=will@kernel.org \
--cc=acme@redhat.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=joey.gouly@arm.com \
--cc=jpoimboe@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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