From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752169AbcEKRcM (ORCPT <rfc822;w@1wt.eu>);
	Wed, 11 May 2016 13:32:12 -0400
Received: from mx2.suse.de ([195.135.220.15]:50523 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751805AbcEKRcL (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 11 May 2016 13:32:11 -0400
Date: Wed, 11 May 2016 19:32:06 +0200
From: Borislav Petkov <bp@suse.de>
To: "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "x86@kernel.org" <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        Andy Lutomirski <luto@kernel.org>,
        "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>,
        "Shankar, Ravi V" <ravi.v.shankar@intel.com>
Subject: Re: [PATCH v6 01/13] x86/xsaves: Define and use fpu_user_xstate_size
Message-ID: <20160511173206.GJ2180@pd.tnic>
References: <cover.1462914897.git.yu-cheng.yu@intel.com>
 <f2e6daf2dc48724cc06250002dc01ac6b30339c1.1462914897.git.yu-cheng.yu@intel.com>
 <20160511172045.GH2180@pd.tnic>
 <3E5A0FA7E9CA944F9D5414FEC6C712205DFABFCA@ORSMSX106.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3E5A0FA7E9CA944F9D5414FEC6C712205DFABFCA@ORSMSX106.amr.corp.intel.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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)
--