lkml.org 
[lkml]   [2022]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v4 0/4] linkage: better symbol aliasing
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

\
 
 \ /
  Last update: 2022-02-22 23:41    [W:0.119 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site