[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 27 Nov 2017 01:23:50 +0000
From: "Liuwenliang (Abbott Liu)" <liuwenliang@...wei.com>
To: Russell King - ARM Linux <linux@...linux.org.uk>
CC: Marc Zyngier <marc.zyngier@....com>,
Mark Rutland <mark.rutland@....com>,
"tixy@...aro.org" <tixy@...aro.org>,
"mhocko@...e.com" <mhocko@...e.com>,
"grygorii.strashko@...aro.org" <grygorii.strashko@...aro.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"glider@...gle.com" <glider@...gle.com>,
"afzal.mohd.ma@...il.com" <afzal.mohd.ma@...il.com>,
"mingo@...nel.org" <mingo@...nel.org>,
Christoffer Dall <cdall@...aro.org>,
"opendmb@...il.com" <opendmb@...il.com>,
"mawilcox@...rosoft.com" <mawilcox@...rosoft.com>,
"kasan-dev@...glegroups.com" <kasan-dev@...glegroups.com>,
Dailei <dylix.dailei@...wei.com>,
"dvyukov@...gle.com" <dvyukov@...gle.com>,
"aryabinin@...tuozzo.com" <aryabinin@...tuozzo.com>,
"labbott@...hat.com" <labbott@...hat.com>,
"vladimir.murzin@....com" <vladimir.murzin@....com>,
"keescook@...omium.org" <keescook@...omium.org>,
"arnd@...db.de" <arnd@...db.de>,
Zengweilin <zengweilin@...wei.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
Heshaoliang <heshaoliang@...wei.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jiazhenghua <jiazhenghua@...wei.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"robin.murphy@....com" <robin.murphy@....com>,
"thgarnie@...gle.com" <thgarnie@...gle.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory
On Nov 23, 2017 23:22 Russell King - ARM Linux [mailto:linux@...linux.org.uk] wrote:
>Please pay attention to the project coding style whenever creating code
>for a program. It doesn't matter what the project coding style is, as
>long as you write your code to match the style that is already there.
>
>For the kernel, that is: tabs not spaces for indentation of code.
>You seem to be using a variable number of spaces for all the new code
>above.
>
>Some of it seems to be your email client thinking it knows better about
>white space - and such behaviours basically makes patches unapplyable.
>See Documentation/process/email-clients.rst for hints about email
>clients.
Thanks for your review.
I'm going to change it in the new version.
Powered by blists - more mailing lists