mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/debug changes for v3.3
Date: Sat, 7 Jan 2012 12:35:45 +0100	[thread overview]
Message-ID: <20120107113545.GA28573@elte.hu> (raw)
In-Reply-To: <CA+55aFzzpMSoRdmqFT7gnH3On43qj8ZVz7C8Dpw6dHB18jtyqw@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Thu, Jan 5, 2012 at 6:47 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > Please pull the latest x86-debug-for-linus git tree from:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-debug-for-linus
> 
> Hell no!
> 
> Why do you send me this sh*t? The "Use NMI instead of 
> REBOOT_VECTOR" commit has been reported to not work AT ALL.
> 
> It was totally broken - Don Zickus sent out the email to fix 
> the completely bogus parenthesis in that commit just a day ago 
> - yet you send me this KNOWN BROKEN CRAP.

My bad.

My primary mistake was that i could have noticed the original 
regression breaking kdump that Yinghai reported - i should have 
delayed the tree until a fix came in - like i delayed a couple 
of other trees that you didn't get sent.

Then, to compound it with another mistake, the fix for the kdump 
breakage was sent to me a couple of hours after i sent you the 
tree - and i havent processed all subsequent mails yet up until 
today - so you noticed it before i did. Double fail.

Anyway, i've queued up the fix and will send you the new tree
after some testing.

> And yes, I checked. The version you sent me is the f*cked one. 
> I was hoping that you would have fixed it up. But no.
> 
> In short, you didn't merge the fix, and yet you sent me a 
> patch series that was *known* to be broken for the last three+ 
> weeks! And I know you were cc'd on the report, which was in 
> the same thread as the automatic tip-bot message for the 
> particular broken commit, so the particular broken commit that 
> introduced it was well-known.
> 
> So that thing has been known broken since before Christmas, 
> and was due to a major typo that made a "atomic_cmpxchg()" not 
> work *at*all* - yet you blithely send me this crap.
> 
> Why? WHAT THE F*CK HAPPENED, INGO?
> 
> Yes, I'm angry as hell. Shit like this should NOT happen.  I 
> don't want people sending me known-buggy pull requests.

You are perfectly right, i messed up - sorry about that.

Thanks,

	Ingo

  reply	other threads:[~2012-01-07 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 14:47 Ingo Molnar
2012-01-06 22:13 ` Linus Torvalds
2012-01-07 11:35   ` Ingo Molnar [this message]
2012-01-08 14:17     ` [GIT PULL, v2] " 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=20120107113545.GA28573@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome