mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ulrich Drepper <drepper@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, pp-manager@sdl.hitachi.co.jp,
	yrl.pp-manager.tt@hitachi.com
Subject: Re: Re: ANDN and Group 17 in x86-opcode-map.txt
Date: Wed, 18 Jan 2012 12:08:40 +0900	[thread overview]
Message-ID: <4F1637B8.8020200@hitachi.com> (raw)
In-Reply-To: <4F15CA4F.9060005@zytor.com>

(2012/01/18 4:21), H. Peter Anvin wrote:
> On 01/17/2012 11:14 AM, Ulrich Drepper wrote:
>> The Intel documentation at
>>
>> http://software.intel.com/file/36945
>>
>> shows the ANDN opcode and Group 17 with encoding f2 and f3 encoding
>> respectively.  The current version of x86-opcode-map.txt shows them
>> with f3 and f4.  Unless someone can point to documentation which shows
>> the currently used encoding the following patch be applied.
>>
>> Signed-off-by: Ulrich Drepper <drepper@gmail.com>
>>
> 
> Looks right to me.  Masami, I assume this was just a transcription error?
> 
> Acked-by: H. Peter Anvin <hpa@zytor.com>

Oh! right, it must be my typo.

Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>



-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2012-01-18  3:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 19:14 Ulrich Drepper
2012-01-17 19:21 ` H. Peter Anvin
2012-01-18  3:08   ` Masami Hiramatsu [this message]
2012-01-17 22:43 ` [tip:x86/urgent] x86, opcode: ANDN and Group 17 in x86-opcode-map. txt tip-bot for Ulrich Drepper

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=4F1637B8.8020200@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=drepper@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pp-manager@sdl.hitachi.co.jp \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yrl.pp-manager.tt@hitachi.com \
    /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