From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, 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: Thu, 17 Feb 2022 11:58:31 +0100 [thread overview]
Message-ID: <Yg4qV6GHaHuLrUmm@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220216162229.1076788-1-mark.rutland@arm.com>
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>
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, 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: Thu, 17 Feb 2022 11:58:31 +0100 [thread overview]
Message-ID: <Yg4qV6GHaHuLrUmm@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220216162229.1076788-1-mark.rutland@arm.com>
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>
_______________________________________________
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-17 11:00 UTC|newest]
Thread overview: 22+ 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 ` 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 ` Mark Rutland
2022-03-09 7:55 ` [tip: x86/core] " tip-bot2 for Mark Rutland
2022-02-16 16:22 ` [PATCH v4 2/4] arm64: clean up symbol aliasing Mark Rutland
2022-02-16 16:22 ` Mark Rutland
2022-03-09 7:55 ` [tip: x86/core] " tip-bot2 for Mark Rutland
2022-02-16 16:22 ` [PATCH v4 3/4] x86: " Mark Rutland
2022-02-16 16:22 ` Mark Rutland
2022-03-09 7:55 ` [tip: x86/core] " tip-bot2 for Mark Rutland
2022-02-16 16:22 ` [PATCH v4 4/4] linkage: remove SYM_FUNC_{START,END}_ALIAS() Mark Rutland
2022-02-16 16:22 ` Mark Rutland
2022-03-09 7:55 ` [tip: x86/core] " tip-bot2 for Mark Rutland
2022-02-17 10:58 ` Peter Zijlstra [this message]
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 10:09 ` Will Deacon
2022-02-22 22:40 ` Will Deacon
2022-02-22 22:40 ` Will Deacon
2022-02-22 22:38 ` Will Deacon
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=Yg4qV6GHaHuLrUmm@hirez.programming.kicks-ass.net \
--to=peterz@infradead.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=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.