From: Ingo Molnar <mingo@elte.hu>
To: ling.ma@intel.com
Cc: hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/2 ] [x86] Modify comments and clean up code.
Date: Fri, 1 Jul 2011 14:40:14 +0200 [thread overview]
Message-ID: <20110701124014.GC12605@elte.hu> (raw)
In-Reply-To: <1309300570-789-1-git-send-email-ling.ma@intel.com>
* ling.ma@intel.com <ling.ma@intel.com> wrote:
> From: Ma Ling <ling.ma@intel.com>
>
> Modern CPU use fast-string instruction to accelerate copy performance,
> by combining data into 128bit, so we modify comments and code style.
>
> Thanks
> Ling
>
> ---
> arch/x86/lib/copy_page_64.S | 124 +++++++++++++++++++++---------------------
> 1 files changed, 62 insertions(+), 62 deletions(-)
Looks good in principle but there's no SOB so i cannot apply it.
Thanks,
Ingo
next prev parent reply other threads:[~2011-07-01 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 22:36 [PATCH RFC 1/2 ] [x86] Modify comments and clean up code ling.ma
2011-07-01 12:40 ` Ingo Molnar [this message]
2011-07-01 20:15 ` Andi Kleen
2011-07-01 20:21 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2012-10-11 12:28 [PATCH RFC 1/2] " ling.ma
2012-10-14 10:49 ` Borislav Petkov
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=20110701124014.GC12605@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=ling.ma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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