LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: TonyWWang-oc <TonyWWang-oc@zhaoxin.com>
To: Borislav Petkov <bp@alien8.de>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"lenb@kernel.org" <lenb@kernel.org>,
	David Wang <DavidWang@zhaoxin.com>,
	"Cooper Yan(BJ-RD)" <CooperYan@zhaoxin.com>,
	"Qiyuan Wang(BJ-RD)" <QiyuanWang@zhaoxin.com>,
	"Herry Yang(BJ-RD)" <HerryYang@zhaoxin.com>
Subject: 答复: [PATCH v1 1/3] x86/cpu: Create Zhaoxin processors architecture support file
Date: Fri, 24 May 2019 08:30:50 +0000	[thread overview]
Message-ID: <a2dffc4698c749f3987efb55dd638509@zhaoxin.com> (raw)
In-Reply-To: <20190523114051.GA3268@cz.tnic>

On Thu, May 23, 2019, Borislav Petkov wrote:
>> This patch is totally corrupted, with leading spaces dropped and tabs
>> turned into spaces.  Please read the email client documentation in the
>> kernel directory for how to fix your email client, or just use 'git
>> send-email' to send the patches out directly.
>
>.. and before you do that, run them all through checkpatch.pl and apply
>common sense when fixing the warnings from it:

Ok, I will run my patches through checkpatch.pl and modify them properly
before resend.

Thanks
TonyWWang-oc

  reply	other threads:[~2019-05-24  8:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b3b31fab04814140b1feb13887c4aa2a@zhaoxin.com>
2019-05-23 10:18 ` gregkh
2019-05-23 10:19 ` gregkh
2019-05-24  8:26   ` 答复: " TonyWWang-oc
2019-05-23 10:24 ` gregkh
2019-05-23 11:40   ` Borislav Petkov
2019-05-24  8:30     ` TonyWWang-oc [this message]
2019-05-24  8:28   ` 答复: " TonyWWang-oc
2019-05-23 13:19 ` Thomas Gleixner
2019-05-24  8:32   ` 答复: " TonyWWang-oc

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=a2dffc4698c749f3987efb55dd638509@zhaoxin.com \
    --to=tonywwang-oc@zhaoxin.com \
    --cc=CooperYan@zhaoxin.com \
    --cc=DavidWang@zhaoxin.com \
    --cc=HerryYang@zhaoxin.com \
    --cc=QiyuanWang@zhaoxin.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --subject='Re: 答复: [PATCH v1 1/3] x86/cpu: Create Zhaoxin processors architecture support file' \
    /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

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).