From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754288AbbGCHG2 (ORCPT ); Fri, 3 Jul 2015 03:06:28 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:36737 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751359AbbGCHGV (ORCPT ); Fri, 3 Jul 2015 03:06:21 -0400 Date: Fri, 3 Jul 2015 00:06:17 -0700 From: Darren Hart To: "Rafael J. Wysocki" Cc: Linus Torvalds , "Rafael J. Wysocki" , Hans de Goede , Linux Kernel Mailing List Subject: Re: [RESEND v2][GIT PULL] platform-drivers-x86 for 4.2-1 Message-ID: <20150703070617.GD5252@fury.dvhart.com> References: <20150630212423.GB27795@vmdeb7> <5216849.vIPuWYcW7k@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5216849.vIPuWYcW7k@vostro.rjw.lan> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 02, 2015 at 09:47:45PM +0200, Rafael Wysocki wrote: > On Wednesday, July 01, 2015 07:04:34 PM Linus Torvalds wrote: > > On Tue, Jun 30, 2015 at 2:24 PM, Darren Hart wrote: > > > > > > other: Use acpi_video_unregister_backlight instead of acpi_video_unregister in > > > serveral drivers. > > > > This was very annoying. > > > > Why? There were several pointless conflicts, because you and Rafael > > both applied some of the same patches from Hans de Goede, and then > > Rafael had further cleanups (also from Hans) on top of that, so as a > > result you have both sides doing changes, but not agreeing on just > > what the changes are. End result: conflict. Ugh! When it rains it pours, I made a mess of this pull request. > > > > The conflicts weren't hard to handle, since generally it was trivial > > to see that "ok, I had already gotten that change and then some" and > > just pick Rafael's side. But it's annoying because it shows that you > > guys are stepping on each others toes, and clearly it's not clear who > > maintains what. > > > > And you guys had clearly both been on the same mail thread, because Unfortunately, the first 3 preparatory patches were contained within platform/drivers/x86, so I picked them up. They arrived well before the broader set of changes which Rafael naturally picked up. > > Rafael had you as acking the changes that you had then also committed > > in your own tree. Please talk to each other so that you know who takes > > what, and we don't have this kind of unnecessary duplication and > > subsequent extra work. I thought I just failed to remove them, but as it turns out... it's worse than that. Michael Ellerman noticed this and reported it, noting he had fixed it up in next and no action was required. As I have been trying to not rebase my next branch per the discussion at Kernel Summit, I interpretted that to mean the fixup was simple enough, and it was better than rebasing the next tree. (So that's the answer to "Why?" above) That was foolish in retrospect... how embarrassing. > > A few duplicate commits aren't the end of the world, so it's not like > > this is a serious problem, but it's an annoyance. > > Sorry about that, we'll coordinate better next time. Apologies for the annoyance. I will be more cognisant of this in the future, and less hesitant to rebase my next branch to avoid such things landing on your plate. Sorry for dragging you through the mud with me Rafael :-/ -- Darren Hart Intel Open Source Technology Center