mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "平松雅巳 / HIRAMATU，MASAMI" <masami.hiramatsu.pt@hitachi.com>
Cc: "'Jiri Olsa'" <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Qiaowei Ren <qiaowei.ren@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/4] x86/insn: perf tools: Add a few new x86 instructions
Date: Wed, 2 Sep 2015 09:39:42 +0200	[thread overview]
Message-ID: <20150902073942.GA6002@gmail.com> (raw)
In-Reply-To: <50399556C9727B4D88A595C8584AAB3752502944@GSjpTKYDCembx32.service.hitachi.net>


* 平松雅巳 / HIRAMATU，MASAMI <masami.hiramatsu.pt@hitachi.com> wrote:

> > sure, np you can use my ack
> 
> I'm also OK for this patch. I just concern that is OK for Adrian too? 
> Since this ensures all the copied code should be dead copy (not modified anymore),
> if we want a different instruction decoding routine, we have to break the test
> anyway.

So the idea would be to not break anything, only warn in a non-fatal question. 
This protects against unbisectable universes being created via simple git merges 
where updates meet but testing of tooling isn't done.

Thanks,

	Ingo

  reply	other threads:[~2015-09-02  7:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 13:58 Adrian Hunter
2015-08-31 13:58 ` [PATCH 1/4] perf tools: Add a test for decoding of " Adrian Hunter
2015-09-01  0:18   ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-01  8:17     ` Adrian Hunter
2015-09-01 11:03       ` 平松雅巳 / HIRAMATU，MASAMI
2015-08-31 13:58 ` [PATCH 2/4] x86/insn: perf tools: Pedantically tweak opcode map for MPX instructions Adrian Hunter
2015-08-31 14:48   ` Arnaldo Carvalho de Melo
2015-08-31 13:58 ` [PATCH 3/4] x86/insn: perf tools: Add new SHA instructions Adrian Hunter
2015-08-31 14:50   ` Arnaldo Carvalho de Melo
2015-08-31 18:58     ` Adrian Hunter
2015-09-01  0:08   ` 平松雅巳 / HIRAMATU，MASAMI
2015-08-31 13:58 ` [PATCH 4/4] x86/insn: perf tools: Add new memory instructions Adrian Hunter
2015-08-31 14:43 ` [PATCH 0/4] x86/insn: perf tools: Add a few new x86 instructions Arnaldo Carvalho de Melo
2015-09-01  8:54 ` Ingo Molnar
2015-09-01 11:38   ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-01 12:10     ` Adrian Hunter
2015-09-01 12:55       ` Ingo Molnar
2015-09-01 15:13       ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-01 12:16   ` Adrian Hunter
2015-09-01 13:56     ` Arnaldo Carvalho de Melo
2015-09-01 13:59     ` Jiri Olsa
2015-09-01 14:55       ` Arnaldo Carvalho de Melo
2015-09-01 19:57     ` Arnaldo Carvalho de Melo
2015-09-02  5:59       ` Jiri Olsa
2015-09-02  6:41         ` 平松雅巳 / HIRAMATU，MASAMI
2015-09-02  7:39           ` Ingo Molnar [this message]
2015-09-02 10:27             ` 平松雅巳 / HIRAMATU，MASAMI

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=20150902073942.GA6002@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=peterz@infradead.org \
    --cc=qiaowei.ren@intel.com \
    --cc=tglx@linutronix.de \
    /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
Powered by JetHome