linux-kernel - Re: [PATCH] APICID: Avoid false sharing on the read mostly x86_cpu_to

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1110252345260.20273@chino.kir.corp.google.com>
Date:	Tue, 25 Oct 2011 23:47:10 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Eial Czerwacki <eial@...lemp.com>
cc:	linux-kernel@...r.kernel.org,
	"Shai Fultheim (Shai@...leMP.com)" <Shai@...lemp.com>
Subject: Re: [PATCH] APICID: Avoid false sharing on the read mostly
 x86_cpu_to_apicid

On Wed, 26 Oct 2011, Eial Czerwacki wrote:

> >> Signed-off-by: Eial Czerwacki<eial@...lemp.com>
> >> Signed-off-by: Shai Fultheim<shai@...lemp.com>
> >> Author: Ravikiran Thirumalai<kiran@...lex86.org>
> > 
> > If the author isn't you, then the patch should start with a single line 
> > that says "From: name <email>" of the author followed by a blank line.  
> > It's also strange that the author doesn't have a sign-off line.
> > 
> 
> 
> the author is mentioned after the last sign-off.
> 

That's not the way it's done, as I said, the patch needs to start with a 
single line like this:

From: Ravikiran Thirumalai <kiran@...lex86.org>

...

and if that person signed it off, then it needs to appear as

Signed-off-by: ...

as the first one in the chain.  Please see part 15 of section 1 of 
Documentation/SubmittingPatches.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/