From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754815AbeARXRy (ORCPT ); Thu, 18 Jan 2018 18:17:54 -0500 Received: from ozlabs.org ([103.22.144.67]:48307 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753881AbeARXRr (ORCPT ); Thu, 18 Jan 2018 18:17:47 -0500 Date: Fri, 19 Jan 2018 10:17:44 +1100 From: Stephen Rothwell To: Thomas Hellstrom Cc: Daniel Vetter , Intel Graphics , DRI , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: Signed-off-by missing for commit in the drm-misc-fixes tree Message-ID: <20180119101744.56515cbf@canb.auug.org.au> In-Reply-To: <8151428f-6e14-4e2b-096f-e258bfb9c9b9@vmware.com> References: <20180119072334.35583121@canb.auug.org.au> <8151428f-6e14-4e2b-096f-e258bfb9c9b9@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, On Thu, 18 Jan 2018 22:18:48 +0100 Thomas Hellstrom wrote: > > That would be me. > I've historically only added my signed-off-by:s on commits I've (co-) > authored myself, as the committer info is already registered, > > But I take it that's not the correct approach? Please read "Developer's Certificate of Origin 1.1" in Documentation/process/submitting-patches.rst. Basically, if you handle the patch on its way to Linus (e.g. commit it to a branch of a git tree that Linus (or someone else along the path) merges) then you need to add a Signed-off-by tag. -- Cheers, Stephen Rothwell