Message-ID: <CAKMK7uHR5wa4xTGkJ8-0_K-j85=VBBEFjuCcbd-u=qU_O9e6Ww@mail.gmail.com>
Date:	Wed, 22 Jun 2016 14:11:25 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Russell King <rmk@...linux.org.uk>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	linux-next <linux-next@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Benjamin Gaignard <benjamin.gaignard@...aro.org>
Subject: Re: [Intel-gfx] linux-next: manual merge of the drm-misc tree with
 the arm tree

On Wed, Jun 22, 2016 at 10:43 AM, Russell King <rmk@...linux.org.uk> wrote:
> On Wed, Jun 22, 2016 at 10:23:36AM +0200, Daniel Vetter wrote:
>> On Wed, Jun 22, 2016 at 09:21:11AM +0100, Russell King wrote:
>> > On Wed, Jun 22, 2016 at 09:31:18AM +0200, Daniel Vetter wrote:
>> > > On Wed, Jun 22, 2016 at 3:47 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> > > > Hi all,
>> > > >
>> > > > Today's linux-next merge of the drm-misc tree got a conflict in:
>> > > >
>> > > >   drivers/gpu/drm/sti/sti_drv.c
>> > > >
>> > > > between commit:
>> > > >
>> > > >   062993b15e8e ("drm: convert DT component matching to component_match_add_release()")
>> > >
>> > > Why did that one end up in the arm tree? Should it go in through
>> > > drm-misc instead?
>> >
>> > Mine is part of a three part patch series which is part of the component
>> > helper updates (which I'm the author and maintainer of).
>> >
>> > Then someone came up with an alternative way of some of part of it.
>> >
>> > You can't merge the above DRM part, because that means you also need to
>> > merge patch 1, which is core component stuff.
>>
>> Makes sense, but generally in that case I ask Dave for an explicit ack for
>> merging through another tree to avoid confusion. Lack of that is why I
>> asked.
>
> It got posted to the appropriate mailing lists with CCs, including David.
> Just three people responded.
>
> One of the responses was that people didn't like the duplication.  I
> posted v2 the same day, the DT people didn't like the file location, so
> I went back to v1.  That then sparked someone to start working _against_
> me, cleaning up the existing duplication, and acknowledging that it'll
> cause _me_ problems.
>
> So, as it was done maliciously and intentionally to give these porblems,
> I'm not budging on this.  Sorry.
>
> There are times when working on the kernel is not very nice.  This is one
> of them.

Please don't jump the gun right away, I just wanted to figure out
what's going on and make sure collaboration and coordination is
working smoothly. At least from what I could see that discussion
didn't happen on dri-devel (or I missed it), so totally didn't know
what's up.

Also, please don't just charge ahead, at least here in the drm
subsystem we try hard to work together and be friendly, and in my
experience there's no isssue at all in getting acks for cases like
this. And really, the conflict with drm-misc seems to be trivial.

But immediately building a castle and marking an aggressive defensive
stance ("I'm not budging on this.") isn't helping anyone. Indeed I
think it's actively harming collaboration and our community,
especially in this case here where I think there wasn't even a problem
to begin with (on the drm side at least, like I said didn't know about
dt). I don't think this is acceptable conduct, next time around please
calm down first before replying in anger. I, and the drm community
here, would really appreciate this.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Powered by blists - more mailing lists