From: Peter Zijlstra <peterz@infradead.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Alexei Starovoitov <ast@kernel.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
Mike Rapoport <rppt@kernel.org>,
linux-toolchains <linux-toolchains@vger.kernel.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Nick Desaulniers <ndesaulniers@google.com>,
bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: linux-next: build warnings after merge of the tip tree
Date: Tue, 22 Mar 2022 08:42:28 +0100 [thread overview]
Message-ID: <Yjl95OMvdCKGvwfT@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAADnVQJnZpQjUv-dw7SU-WwTOn_tZ8xmy5ydRn=g_m-9UyS2kw@mail.gmail.com>
On Mon, Mar 21, 2022 at 03:12:05PM -0700, Alexei Starovoitov wrote:
>
> That makes little sense. It's not an unusual merge conflict.
It is not only that; it is adding code that with an x86 arch maintainer
hat on I've never seen and don't agree with. Same for arm64 apparently.
prev parent reply other threads:[~2022-03-22 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220321140327.777f9554@canb.auug.org.au>
[not found] ` <Yjh11UjDZogc3foM@hirez.programming.kicks-ass.net>
[not found] ` <Yjh3xZuuY3QcZ1Bn@hirez.programming.kicks-ass.net>
[not found] ` <Yjh4xzSWtvR+vqst@hirez.programming.kicks-ass.net>
[not found] ` <YjiBbF+K4FKZyn6T@hirez.programming.kicks-ass.net>
[not found] ` <YjiZhRelDJeX4dfR@hirez.programming.kicks-ass.net>
[not found] ` <YjidpOZZJkF6aBTG@hirez.programming.kicks-ass.net>
[not found] ` <CAHk-=wigO=68WA8aMZnH9o8qRUJQbNJPERosvW82YuScrUTo7Q@mail.gmail.com>
[not found] ` <YjirfOJ2HQAnTrU4@hirez.programming.kicks-ass.net>
[not found] ` <CAHk-=wguO61ACXPSz=hmCxNTzqE=mNr_bWLv6GH5jCVZLBL=qw@mail.gmail.com>
2022-03-21 22:05 ` linux-next: build warnings after merge of the tip tree Stephen Rothwell
2022-03-21 22:12 ` Alexei Starovoitov
2022-03-21 22:46 ` Stephen Rothwell
2022-03-21 22:50 ` Alexei Starovoitov
2022-03-21 22:55 ` Steven Rostedt
2022-03-22 4:51 ` Masami Hiramatsu
2022-03-22 4:53 ` Alexei Starovoitov
2022-03-22 7:42 ` Peter Zijlstra [this message]
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=Yjl95OMvdCKGvwfT@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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