[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160511173206.GJ2180@pd.tnic>
Date: Wed, 11 May 2016 19:32:06 +0200
From: Borislav Petkov <bp@...e.de>
To: "Yu, Fenghua" <fenghua.yu@...el.com>
Cc: "Yu, Yu-cheng" <yu-cheng.yu@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
"Prakhya, Sai Praneeth" <sai.praneeth.prakhya@...el.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>
Subject: Re: [PATCH v6 01/13] x86/xsaves: Define and use fpu_user_xstate_size
On Wed, May 11, 2016 at 05:25:17PM +0000, Yu, Fenghua wrote:
> Is this possible to have the third one?
>
> From: Yu-cheng
>
> Signed-off-by: Yu-cheng
> Signed-off-by: Fenghua
This SOB chain says that Yu-cheng is the author and then you've received
it from him, have done something to it (which we sometimes put in [] to
denote it) and then you've sent it out.
The tip maintainer which applies it will add his SOB too, at the end.
Let me ask you this: what exactly do you want to express with the SOB
chain?
Just a reminder: the SOB chain should give a clear and precise
representation of the patch path from author to upstream.
Section
11) Sign your work
------------------
in Documentation/SubmittingPatches explains the whole story.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
Powered by blists - more mailing lists