From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm: objtool warning
Date: Thu, 13 Jun 2019 09:06:36 -0500 [thread overview]
Message-ID: <20190613140636.nokozwltmqrmyrin@treble> (raw)
In-Reply-To: <5baaf9ec-8ea7-544c-49d1-dde519d919ca@infradead.org>
On Wed, Jun 12, 2019 at 07:57:43PM -0700, Randy Dunlap wrote:
> In yesterday's mmotm, I see this objtool warning:
>
> arch/x86/entry/entry_64.o: warning: objtool: .entry.text+0x908: unreachable instruction
I think it's this one again:
https://lkml.kernel.org/r/15ed85f4-bf2e-da91-71c1-46875d1c6e3f@infradead.org
I still can't reproduce it, and I still don't understand it...
--
Josh
prev parent reply other threads:[~2019-06-13 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 2:57 mmotm: objtool warning Randy Dunlap
2019-06-13 14:06 ` Josh Poimboeuf [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=20190613140636.nokozwltmqrmyrin@treble \
--to=jpoimboe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@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