From: Andi Kleen <ak@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: jpoimboe@redhat.com, jbaron@akamai.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] static_call: Use single copy of static_call_return0
Date: Mon, 26 Apr 2021 07:47:57 -0700 [thread overview]
Message-ID: <20210426144757.GV1401198@tassilo.jf.intel.com> (raw)
In-Reply-To: <YIZ2/2H4W1U5DNBm@hirez.programming.kicks-ass.net>
> This is ARCH=i386 only afaict, why do we care?
Well I'm trying to make LTO build even for 32bit.
Besides the bug with self test is real everywhere.
But looks like the patch didn't apply (I had some earlier
patches which were apparently needed). I'll rebase and repost.
-Andi
prev parent reply other threads:[~2021-04-26 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 21:11 [PATCH] static_call: Use single copy of static_call_return0 Andi Kleen
2021-04-26 8:17 ` Peter Zijlstra
2021-04-26 14:47 ` Andi Kleen [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=20210426144757.GV1401198@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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