Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751113AbaADFLc (ORCPT ); Sat, 4 Jan 2014 00:11:32 -0500 Received: from mail-qc0-f179.google.com ([209.85.216.179]:61672 "EHLO mail-qc0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750794AbaADFLa (ORCPT ); Sat, 4 Jan 2014 00:11:30 -0500 MIME-Version: 1.0 X-Originating-IP: [173.13.129.225] In-Reply-To: <52AECF56.8020508@atmel.com> References: <20131216104738.6f845aabd0e3b609ed9ca170@canb.auug.org.au> <52AECF56.8020508@atmel.com> Date: Fri, 3 Jan 2014 21:11:29 -0800 Message-ID: Subject: Re: linux-next: manual merge of the renesas tree with the arm-soc tree From: Olof Johansson To: Nicolas Ferre 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 , Mike Turquette Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1787 Lines: 47 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. :) -Olof -- 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/