Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946232AbbEVJhc (ORCPT ); Fri, 22 May 2015 05:37:32 -0400 Received: from mout.kundenserver.de ([212.227.17.13]:49671 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946188AbbEVJh1 convert rfc822-to-8bit (ORCPT ); Fri, 22 May 2015 05:37:27 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Stefan Agner , Uwe =?ISO-8859-1?Q?Kleine=2DK=F6nig?= , Russell King - ARM Linux , Joachim Eastwood , linux-kernel@vger.kernel.org, Maxime Coquelin , Olof Johansson Subject: Re: [PATCH soc] ARM: use ARM_SINGLE_ARMV7M for ARMv7-M platforms Date: Fri, 22 May 2015 11:37:21 +0200 Message-ID: <8411283.ijzXxHBtEc@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1890f941dfa59138442da3e80a6b492a@agner.ch> References: <1432161344-1930-1-git-send-email-stefan@agner.ch> <20150521190400.GD24769@pengutronix.de> <1890f941dfa59138442da3e80a6b492a@agner.ch> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" X-Provags-ID: V03:K0:taJDfSTCOYIU1+nu/++70A1XGniVAFmsFhxZFDMDQ/yMdcjhyhD y9Ks5fg3OTlGZ/uM4S1wbEY/cLoyvMWTlfDBkLb1iHVRr16ivkk4vBC+yiw0nEgBGnwF2Nk lqzHQktlzE6xqu+l7mndKcq6Dtfao7nokr8tEWAomVIpADsv2DYltRlooYtovqx+swfzYYH YY5AhnehJncUjAyNGry6Q== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2505 Lines: 53 On Friday 22 May 2015 09:27:38 Stefan Agner wrote: > On 2015-05-21 21:04, Uwe Kleine-K?nig wrote: > > On Thu, May 21, 2015 at 07:00:02PM +0200, Joachim Eastwood wrote: > >> Hi Stefan, > >> > >> On 21 May 2015 at 00:35, Stefan Agner wrote: > >> > Use the new config symbol ARM_SINGLE_ARMV7M which groups config > >> > symbols used by modern ARMv7-M platforms. This allows supporting > >> > multiple ARMv7-M platforms in one kernel image. However, a common > >> > kernel image requires the combined platforms to share the same > >> > main memory layout to be bootable. > >> > > >> > Acked-by: Uwe Kleine-K?nig > >> > Signed-off-by: Stefan Agner > >> > >> You should have your sign-off on the top and not Uwe's ack. > > I don't agree. IMHO the most sensible thing is to sign off (i.e. put > > your sob line below) all the things that come from you. So it's > > > > Signed-off-by: author > > Acked-by: someone > > Signed-off-by: forwarder > > Signed-off-by: maintainer > > > > if someone already acked before forwarder sent out the mail. If the ack > > is between forwarder and maintainer it was the latter who added the Ack. > > I'm not sure it's formalized this way, but like that it makes most sense > > to me and I seem to recall having read somewhere that the footers are > > supposed to tell something about the order of people involved. > > > > So Stefan did it exactly as i would have done it. > > Hm, never give much thoughts about that order, its quite development > process driven here: I use git format-patch with --signoff. When I send > out v1, and get a Ack or Review, I add that to my commit. Hence, when I > send v2 of the patch, my sob line ends up below the Ack (that is what > happened in that case). If its the last revision, and the patch gets > picked up, the forwarder/maintainer will add the Ack and then it would > land after my sob... I think it's not very important either way. The order that Uwe suggested is what we tend to end up with when everyone just adds additional tags on the bottom, but I also see the acks added elsewhere. The order for the signed-off-by lines is more important though, as it documents the patch flow. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/