From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
hpa@zytor.com, jeremy.fitzhardinge@citrix.com, mingo@redhat.com,
stable@kernel.org, tglx@linutronix.de,
Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [Xen tree maintenance] Re: Not really merged? Re: [merged] x86-paravirt-pte-updates-in-kunmap_atomic-need-to-be-synchronous-regardless-of-lazy_mmu-mode.patch removed from -mm tree
Date: Fri, 28 Oct 2011 09:59:26 -0400 [thread overview]
Message-ID: <20111028135926.GB6509@phenom.dumpdata.com> (raw)
In-Reply-To: <20111028074810.GB27593@elte.hu>
> > commit ab67482036cee590753dd42b7f66aada97e6dcde
> > Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > AuthorDate: Fri Sep 23 17:02:29 2011 -0400
> > Commit: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > CommitDate: Mon Sep 26 09:12:37 2011 -0400
Aha! And I am not sure why I put that in my #linux-next branch. That
is not good - thanks for identifying the cause of that patch being
dropped, and I am sorry for pushing it there without getting the
proper Acks.
>
> ARGH!
>
> Konrad, STOP THIS CRAP!
>
> This is the Nth time you have interefered with the x86 tree's
> workflow - and now you have caused patch loss in -mm.
>
> I'll have to insist on the Xen tree being merged via the x86 tree
> again, this clearly does not work, your maintenance practices are
> VERY incompetent and you are not learning.
>
> The rule is very simple: don't EVER push anything arch/x86/ into
> linux-next that is outside the arch/x86/xen/ and
> arch/x86/include/asm/xen/ patterns, without very clear acks from the
> x86 maintainers and a binding promise to carry that patch upstream!
Of course.
If you have some time, can you tell me what other times this has
caused trouble? I remember Jeremy did a mistake some time ago
(so patch with a very very old time date) that screwed up something.
And .... oh, the compile time one that Randy found and it did not get
fixed for some very emberassingly long time. If I remember right that was
in Jeremy's tree (xen) - not mine (xen-two):
http://marc.info/?i=20110804193534.GB12729@elte.hu
We do have _two_ Xen trees (xen and xen-two) - which is not making things
easier to figure out who is at fault for what.
You would not have a good overview of maintainer practices so that both
me and Jeremy can refresh our memory of what to do and especially
what _not_ to do?
next prev parent reply other threads:[~2011-10-28 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 19:51 [merged] x86-paravirt-pte-updates-in-kunmap_atomic-need-to-be-synchronous-regardless-of-lazy_mmu-mode.patch removed from -mm tree akpm
2011-10-25 18:24 ` Not really merged? " Konrad Rzeszutek Wilk
2011-10-27 22:53 ` Andrew Morton
2011-10-28 7:08 ` Ingo Molnar
2011-10-28 7:39 ` Andrew Morton
2011-10-28 7:48 ` [Xen tree maintenance] " Ingo Molnar
2011-10-28 13:59 ` Konrad Rzeszutek Wilk [this message]
2011-10-28 14:33 ` Konrad Rzeszutek Wilk
2011-11-30 11:02 ` Stefan Bader
2011-11-30 19:41 ` Andrew Morton
2011-12-05 15:56 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111028135926.GB6509@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.