linux-kernel - Re: [PATCH] x86:kernel:e820c:kmemdup instead of duplicating its function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190108133048.GC14243@zn.tnic>
Date:   Tue, 8 Jan 2019 14:30:48 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Yi Wang <wang.yi59@....com.cn>
Cc:     tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
        x86@...nel.org, akpm@...ux-foundation.org, rppt@...ux.vnet.ibm.com,
        mhocko@...e.com, pavel.tatashin@...rosoft.com, joe@...ches.com,
        jschoenh@...zon.de, m.mizuma@...fujitsu.com,
        n-horiguchi@...jp.nec.com, linux-kernel@...r.kernel.org,
        xue.zhihong@....com.cn, "huang.zijiang" <huang.zijiang@....com.cn>
Subject: Re: [PATCH] x86:kernel:e820c:kmemdup instead of duplicating its
 function

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