From: Josh Poimboeuf <jpoimboe@kernel.org>
To: tip-bot2 for Ingo Molnar <tip-bot2@linutronix.de>
Cc: linux-tip-commits@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org
Subject: Re: [tip: objtool/core] x86/orc: Make the is_callthunk() definition depend on CONFIG_BPF_JIT=y
Date: Fri, 9 Jun 2023 14:24:20 -0700 [thread overview]
Message-ID: <20230609212420.ida7mc2w3xxij3h4@treble> (raw)
In-Reply-To: <168630229338.404.8674192988459787200.tip-bot2@tip-bot2>
On Fri, Jun 09, 2023 at 09:18:13AM -0000, tip-bot2 for Ingo Molnar wrote:
> The following commit has been merged into the objtool/core branch of tip:
>
> Commit-ID: 301cf77e21317b3465c5e2bb0188df24bbf1c2e2
> Gitweb: https://git.kernel.org/tip/301cf77e21317b3465c5e2bb0188df24bbf1c2e2
> Author: Ingo Molnar <mingo@kernel.org>
> AuthorDate: Fri, 09 Jun 2023 11:04:53 +02:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Fri, 09 Jun 2023 11:09:04 +02:00
>
> x86/orc: Make the is_callthunk() definition depend on CONFIG_BPF_JIT=y
>
> Recent commit:
>
> 020126239b8f Revert "x86/orc: Make it callthunk aware"
>
> Made the only user of is_callthunk() depend on CONFIG_BPF_JIT=y, while
> the definition of the helper function is unconditional.
>
> Move is_callthunk() inside the #ifdef block.
>
> Addresses this build failure:
>
> arch/x86/kernel/callthunks.c:296:13: error: ‘is_callthunk’ defined but not used [-Werror=unused-function]
Sorry about that. The bots didn't complain for some reason :-/
--
Josh
next prev parent reply other threads:[~2023-06-09 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 9:18 [tip: objtool/core] x86/orc: Make the is_callthunk() definition depend on CONFIG_BPF_JIT=y tip-bot2 for Ingo Molnar
2023-06-09 21:24 ` Josh Poimboeuf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 9:10 tip-bot2 for Ingo Molnar
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=20230609212420.ida7mc2w3xxij3h4@treble \
--to=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tip-bot2@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).