From: "H. Peter Anvin" <hpa@zytor.com>
To: "Ma, Ling" <ling.ma@intel.com>
Cc: Namhyung Kim <namhyung@gmail.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: Re: [PATCH V2] [X86] Fix potential issue on memmove
Date: Thu, 12 Aug 2010 07:15:25 -0700 [thread overview]
Message-ID: <4C6401FD.1050600@zytor.com> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F0E483AD918@shsmsx502.ccr.corp.intel.com>
On 08/11/2010 11:52 PM, Ma, Ling wrote:
> Thanks, I will fix it in next version.
Also, please split this into two patches -- one for fixing memmove, and
the other for re-enabling the alias avoidance in memcpy.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-08-12 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 6:48 [PATCH V2] [X86] Fix potential issue on memmove Namhyung Kim
2010-08-12 6:52 ` Ma, Ling
2010-08-12 14:15 ` H. Peter Anvin [this message]
2010-08-12 14:22 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2010-08-11 22:20 ling.ma
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=4C6401FD.1050600@zytor.com \
--to=hpa@zytor.com \
--cc=ling.ma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.