From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Your action on perf bug report is requested was Re: Basic perf PMU support for Haswell v11
Date: Wed, 1 May 2013 12:33:19 +0200 [thread overview]
Message-ID: <20130501103319.GB17360@gmail.com> (raw)
In-Reply-To: <20130501101041.GG17814@two.firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> > I found a similar system (not same stepping, but same model) and tested
> > perf top works fine here. Also on a couple of other systems.
> >
> > Since I cannot reproduce I would need your help debugging it.
>
> Ingo, I haven't heard back from you on this.
FYI, the v3.10 merge window has started 3+ days ago.
The merge window is a very busy time period for Linus and maintainers
alike, and developers should generally not expect maintainers to deal with
new experimental patches near to or especially during the merge window!
As a special exception I tried and tested your patches on Friday and
reported back to you the bug, 2 days before the opening of the merge
window - but you should not expect out of order treatment of development
patches during the merge window
I might have time to look at your patches in a few days. No promises - I
still haven't merged all trees to Linus. I think the 11 review cycles of
your Haswell patch-set are proof enough of my willingness to deal with
your patches.
> You reported an unreproducable bug. I gave you several steps to diagnose
> the problem, so that we can make progress on this.
It's entirely reproducible here on that testbox, and was caused by your
patches - I partially bisected it to your series. (but not to a specific
patch in your series - ran out of time.)
> You've had several days time now to to this, but I have not heard from
> you.
FYI, you are entirely confused about how Linux maintenance works near and
during the merge window. Many maintainers don't take any patches but only
take fixes for already applied patches. (In -tip we generally try to
freeze a week before the merge window, so your patches missed the v3.10
merge window by a wide margin I'm afraid.)
Furthermore, frankly, the nasty, demanding tone of your mail, expecting
and demanding a reply to your mail within two work days (!) is ridiculous
and unacceptable and does not make it more likely for me to make special
exceptions for your patches.
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-01 10:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 19:06 Basic perf PMU support for Haswell v11 Andi Kleen
2013-04-20 19:06 ` [PATCH 1/5] perf, x86: Add Haswell PEBS record support v5 Andi Kleen
2013-04-20 19:06 ` [PATCH 2/5] perf, x86: Basic Haswell PMU support v8 Andi Kleen
2013-04-20 19:06 ` [PATCH 3/5] perf, x86: Basic Haswell PEBS support v4 Andi Kleen
2013-04-20 19:06 ` [PATCH 4/5] perf, x86: Move NMI clearing to end of PMI handler after the counter registers are reset Andi Kleen
2013-04-20 19:06 ` [PATCH 5/5] perf, x86: Support Haswell v4 LBR format v2 Andi Kleen
2013-09-03 19:25 ` Vince Weaver
2013-09-03 20:28 ` Andi Kleen
2013-09-03 21:14 ` Vince Weaver
2013-09-03 22:37 ` Andi Kleen
2013-09-04 14:21 ` Vince Weaver
2013-09-04 17:05 ` Andi Kleen
2013-04-26 6:55 ` Basic perf PMU support for Haswell v11 Ingo Molnar
2013-04-26 6:59 ` Ingo Molnar
2013-05-01 10:48 ` Ingo Molnar
2013-04-26 22:52 ` Andi Kleen
2013-05-01 10:10 ` Your action on perf bug report is requested was " Andi Kleen
2013-05-01 10:33 ` Ingo Molnar [this message]
2013-05-02 8:38 ` Ingo Molnar
2013-05-02 8:49 ` 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=20130501103319.GB17360@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).