From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "peterz@infradead.org" <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Poimboe, Josh" <jpoimboe@redhat.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: IBT related objtool warnings
Date: Thu, 7 Apr 2022 16:11:41 +0000 [thread overview]
Message-ID: <77bba8d6aca596f7d5edc576c74ab9326b061bb7.camel@intel.com> (raw)
In-Reply-To: <20220407160715.GB2762@worktop.programming.kicks-ass.net>
On Thu, 2022-04-07 at 18:07 +0200, Peter Zijlstra wrote:
> And this for gcc-8.4
It's fixed.
Thanks,
Rick
prev parent reply other threads:[~2022-04-07 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 22:43 IBT related objtool warnings Edgecombe, Rick P
2022-04-07 6:49 ` Peter Zijlstra
2022-04-07 15:20 ` Edgecombe, Rick P
2022-04-07 15:51 ` Peter Zijlstra
2022-04-07 16:07 ` Peter Zijlstra
2022-04-07 16:11 ` Edgecombe, Rick P [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=77bba8d6aca596f7d5edc576c74ab9326b061bb7.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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