linux-kernel - Re: [GIT pull] irq fixes for 2.6.31

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0908182235500.3361@localhost.localdomain>
Date:	Tue, 18 Aug 2009 22:37:36 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [GIT pull] irq fixes for 2.6.31

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/