From: Borislav Petkov <bp@alien8.de>
To: Yi Wang <wang.yi59@zte.com.cn>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, akpm@linux-foundation.org,
rppt@linux.vnet.ibm.com, mhocko@suse.com,
pavel.tatashin@microsoft.com, joe@perches.com,
jschoenh@amazon.de, m.mizuma@jp.fujitsu.com,
n-horiguchi@ah.jp.nec.com, linux-kernel@vger.kernel.org,
xue.zhihong@zte.com.cn,
"huang.zijiang" <huang.zijiang@zte.com.cn>
Subject: Re: [PATCH] x86:kernel:e820c:kmemdup instead of duplicating its function
Date: Tue, 8 Jan 2019 14:30:48 +0100 [thread overview]
Message-ID: <20190108133048.GC14243@zn.tnic> (raw)
In-Reply-To: <1546926137-32136-1-git-send-email-wang.yi59@zte.com.cn>
> Subject: Re: [PATCH] x86:kernel:e820c:kmemdup instead of duplicating its function
The tip tree preferred format for patch subject prefixes is
'subsys/component:', e.g. 'x86/apic:', 'x86/mm/fault:', 'sched/fair:',
'genirq/core:'. Please do not use file names or complete file paths as
prefix. 'git log path/to/file' should give you a reasonable hint in most
cases.
The condensed patch description in the subject line should start with a
uppercase letter and should be written in imperative tone.
On Tue, Jan 08, 2019 at 01:42:17PM +0800, Yi Wang wrote:
> From: "huang.zijiang" <huang.zijiang@zte.com.cn>
^^^^^^^^^^^^^^
I'm guessing your name is "Huang Zijiang" and you'd like to have it this
way in git history, instead with small letters and with a dot inbetween?
> kmemdup has implemented the function that kmalloc() and memcpy().
This is not a correct english sentence. Please try again.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2019-01-08 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 5:42 [PATCH] x86:kernel:e820c:kmemdup instead of duplicating its function Yi Wang
2019-01-08 13:30 ` Borislav Petkov [this message]
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=20190108133048.GC14243@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=huang.zijiang@zte.com.cn \
--cc=joe@perches.com \
--cc=jschoenh@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.mizuma@jp.fujitsu.com \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=pavel.tatashin@microsoft.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=wang.yi59@zte.com.cn \
--cc=x86@kernel.org \
--cc=xue.zhihong@zte.com.cn \
/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