From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86 <x86@kernel.org>
Subject: Re: [PATCH 1/1] x86/tools: Use tools headers for instruction decoder selftests
Date: Fri, 6 Nov 2020 11:52:31 -0600 [thread overview]
Message-ID: <20201106175231.f64g7c6f47gq2mty@treble> (raw)
In-Reply-To: <20201106112413.80248e44fef68d9acf932dec@kernel.org>
On Fri, Nov 06, 2020 at 11:24:13AM +0900, Masami Hiramatsu wrote:
> > Right, this is expected. The patch is based on jpoimboe/objtool/core,
> > which has extra commits.
>
> Has that series already submitted to LKML? I need to look at the series too.
> Or, Josh, can you review it and if it is OK, please pick it to your series
> and send it.
I believe those patches were dropped from -tip because of a build issue.
Vasily, can you repost fixed versions of those patches, based on
tip/objtool/core, along with this new patch?
--
Josh
next prev parent reply other threads:[~2020-11-06 17:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 16:20 [tip: objtool/core] x86/insn: Support big endian cross-compiles tip-bot2 for Martin Schwidefsky
2020-10-09 20:38 ` Peter Zijlstra
2020-10-09 20:49 ` Borislav Petkov
2020-10-10 14:02 ` Vasily Gorbik
2020-10-11 14:40 ` Borislav Petkov
2020-10-12 0:02 ` Masami Hiramatsu
2020-10-10 17:44 ` Josh Poimboeuf
2020-10-12 0:12 ` Masami Hiramatsu
2020-10-12 15:39 ` Josh Poimboeuf
2020-10-14 7:28 ` Masami Hiramatsu
2020-10-15 6:24 ` Ian Rogers
2020-11-03 19:35 ` Vasily Gorbik
2020-11-03 19:35 ` [PATCH 1/1] x86/tools: Use tools headers for instruction decoder selftests Vasily Gorbik
2020-11-04 9:11 ` kernel test robot
2020-11-04 9:18 ` Vasily Gorbik
2020-11-06 2:24 ` Masami Hiramatsu
2020-11-06 17:52 ` Josh Poimboeuf [this message]
2020-11-04 11:54 ` kernel test robot
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=20201106175231.f64g7c6f47gq2mty@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=clang-built-linux@googlegroups.com \
--cc=gor@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@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
all inboxes | Powered by JetHome®