From: Masami Hiramatsu <mhiramat@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org,
tip-bot2 for Masami Hiramatsu <tip-bot2@linutronix.de>,
linux-tip-commits@vger.kernel.org,
syzbot+9b64b619f10f19d19a7c@syzkaller.appspotmail.com,
Borislav Petkov <bp@suse.de>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/uprobes: Do not use prefixes.nbytes when looping over prefixes.bytes
Date: Sun, 6 Dec 2020 12:53:25 +0900 [thread overview]
Message-ID: <20201206125325.d676906774c2329742746005@kernel.org> (raw)
In-Reply-To: <20201205101704.GB26409@zn.tnic>
On Sat, 5 Dec 2020 11:17:04 +0100
Borislav Petkov <bp@alien8.de> wrote:
> On Sat, Dec 05, 2020 at 09:12:56AM +0900, Masami Hiramatsu wrote:
> > This may break tools/objtool build. Please keep "inat.h".
>
> How? Please elaborate.
>
> Build tests are fine here.
Oops, sorry, it was for perf build.
Please refer commit 00a263902ac3 ("perf intel-pt: Use shared x86 insn decoder").
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-12-06 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <160697103739.3146288.7437620795200799020.stgit@devnote2>
2020-12-04 15:04 ` [tip: x86/urgent] x86/uprobes: Do not use prefixes.nbytes when looping over prefixes.bytes tip-bot2 for Masami Hiramatsu
2020-12-05 0:12 ` Masami Hiramatsu
2020-12-05 10:17 ` Borislav Petkov
2020-12-06 3:53 ` Masami Hiramatsu [this message]
2020-12-09 18:05 ` Arnaldo Carvalho de Melo
2020-12-06 9:09 ` tip-bot2 for Masami Hiramatsu
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=20201206125325.d676906774c2329742746005@kernel.org \
--to=mhiramat@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+9b64b619f10f19d19a7c@syzkaller.appspotmail.com \
--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 NNTP newsgroup(s).