mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [GIT pull] irq fixes for 2.6.31
Date: Tue, 18 Aug 2009 22:37:36 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0908182235500.3361@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.01.0908181330210.3158@localhost.localdomain>

On Tue, 18 Aug 2009, Linus Torvalds wrote:
> On Mon, 17 Aug 2009, Thomas Gleixner wrote:
> > 
> > I have no idea what went wrong this time. I force pushed the branch
> > and pulled it back on a test machine to compile and test boot. The
> > test machine still has the correct sha1 for that branch while
> > master.kernel.org did not. I probably pushed out some other branch
> > between the point where I sent the pull request and the time you
> > pulled, but I can not find any hint in my bash history which would
> > explain why it wreckaged the irq-fixes-for-linus branch.
> > 
> > Just double checked that it is pushed out to git://.... as well.
> 
> It's still wrong. 
> 
> 	http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=irq-fixes-for-linus
> 
> still does _not_ show that
> 
> 	genirq: Do not wakeup irq thread from __setup_irq() and set action->irq
> 
> commit, but the broken one.

Err, no. Please see the mail I sent an hour ago.

Even the http.... interface shows the one I want you to pull:

     69ab849439b506cd8dd2879527fdb64d95dd5211

Thanks,

	tglx

  reply	other threads:[~2009-08-18 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 19:27 Thomas Gleixner
2009-08-17 20:42 ` Linus Torvalds
2009-08-17 21:52   ` Thomas Gleixner
2009-08-18 20:33     ` Linus Torvalds
2009-08-18 20:37       ` Thomas Gleixner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-18 19:31 Thomas Gleixner
2009-07-22 21:22 Thomas Gleixner

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=alpine.LFD.2.00.0908182235500.3361@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®