Re: linux-next: manual merge of the arm tree with Linus' tree
From: Ingo Molnar
Date: Tue Mar 13 2012 - 04:48:16 EST
* Russell King <rmk@xxxxxxxxxxxxxxxx> wrote:
> Please check your mailbox:
>
> Date: Fri, 20 Jan 2012 17:42:27 +0000
> From: Catalin Marinas <catalin.marinas@xxxxxxx>
> To: linux-kernel@xxxxxxxxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> Cc: Russell King <linux@xxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>,
> Peter Zijlstra <peterz@xxxxxxxxxxxxx>,
> Will Deacon <will.deacon@xxxxxxx>,
> Frank Rowand <frank.rowand@xxxxxxxxxxx>
> Subject: [PATCH v3 1/6] sched: Introduce the finish_arch_post_lock_switch()
> scheduler hook
Btw., are you losing emails? Because the reply from peterz to
those patches, a month ago, was pretty clear:
> > Russell, what's the status of these patches? I'd like to see
> > them land in 3.4 if possible. I'm fine either way, I'll
> >
> > probably ask Ingo to pull your tree so that I can stack some
> > other patches on top.
You never replied to PeterZ's request, you just ignored this
scheduler maintainer request and you just did it in some random
way that was most convenient to you many weeks after the thread
died down, ignoring everyone else's concerns - a pretty usual
pattern from you I have to say.
Had you followed PeterZ's request this conflict in linux-next
could have been avoided, amongst other things.
Given that the merge window is close I doubt there will be
other, more difficult to resolve conflicts, but this incident
again demonstrates your inability to communicate efficiently and
amicably, forcing me to highlight it in this trivial case
because it's a sadly reoccuring pattern.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/