Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756903AbaAHQ4p (ORCPT ); Wed, 8 Jan 2014 11:56:45 -0500 Received: from mail-yh0-f49.google.com ([209.85.213.49]:49944 "EHLO mail-yh0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932119AbaAHQ4l convert rfc822-to-8bit (ORCPT ); Wed, 8 Jan 2014 11:56:41 -0500 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT To: Nicolas Ferre , "Olof Johansson" From: Mike Turquette In-Reply-To: <52CA7AFB.9010208@atmel.com> Cc: "Stephen Rothwell" , "Simon Horman" , "Arnd Bergmann" , "linux-arm-kernel@lists.infradead.org" , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Boris BREZILLON" , "Laurent Pinchart" References: <20131216104738.6f845aabd0e3b609ed9ca170@canb.auug.org.au> <52AECF56.8020508@atmel.com> <52CA7AFB.9010208@atmel.com> Message-ID: <20140108165634.27803.31368@quantum> User-Agent: alot/0.3.5 Subject: Re: linux-next: manual merge of the renesas tree with the arm-soc tree Date: Wed, 08 Jan 2014 08:56:34 -0800 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Nicolas Ferre (2014-01-06 01:44:27) > On 04/01/2014 06:11, Olof Johansson : > > On Mon, Dec 16, 2013 at 2:00 AM, Nicolas Ferre wrote: > >> On 16/12/2013 00:47, Stephen Rothwell : > >>> Hi Simon, > >>> > >>> Today's linux-next merge of the renesas tree got a conflict in > >>> drivers/clk/Makefile between commit 0ad6125b1579 ("clk: at91: add PMC > >>> base support") from the arm-soc tree and commit 10cdfe9f327a ("clk: > >>> shmobile: Add R-Car Gen2 clocks support") from the renesas tree. > >>> > >>> I fixed it up (see below) and can carry the fix as necessary (no action > >>> is required). > >> > >> Fine for me. > > > > Simon, Nicolas, > > > > > > > > While a very minor issue, this should have been altogether avoided > > with a little more attention when applying patches. The Makefile is > > sorted, and you've appended new lines to the end instead of in the > > place they're supposed to go. Sure, others have done the same mistake > > in a few places but that doesn't mean we shouldn't try to keep it > > sorted. > > > > The very reason _to_ sort a Makefile is to avoid these needless > > add-add conflicts when two people append to the same unsorted list. > > > > Now I can't resolve it properly and move the entries when I do the > > same merge (and get the same conflict), because that will cause a > > third conflict for Stephen, and he's about to return from vacation and > > is going to cuss at us if we cause too many new conflicts in one day. > > :) > > > > > > > > So, best choice is to keep the unsortedness now, and have Mike resort > > his Makefile for us at the end of the merge window. And keep a little > > closer eye on Makefile and Kconfig additions in the future. :) > > Totally agree in keeping a Makefile sorted, when it is already sorted. > What I recall having thought when I had seen this Makefile is: well this > one must be of the "append your changes to the end" type... > > Anyway be sure that I will pay attention to this. The file used to be sorted. I've cleaned it up locally and will apply the patch after I take in a few more pull requests. Regards, Mike > > Bye, > -- > Nicolas Ferre -- 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/