linux-kernel - Re: linux-next: manual merge of the lost-spurious-irq tree with the tip tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CAACCC1.6000000@kernel.org>
Date:	Tue, 05 Oct 2010 08:59:13 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: linux-next: manual merge of the lost-spurious-irq tree with the
 tip tree

On 10/05/2010 08:55 AM, Tejun Heo wrote:
> I think Stephen had done enough.  At the time, I wasn't sure which
> tree it was going to go through and it took some time before Thomas
> responded, so I was intending to push it through separately.  I should
> have retracted the tree right after it was determined to be
> reimplemented but forgot.  That's my mistake not Stephen's.  Sorry
> about that.

Oooh, apparently I knew it was gonna go through genirq but expected it
to go through as-is and wanted to accelerate testing.  FWIW, I'm
sure everyone involved was notified of the move at the time.  At any
rate, won't happen again.

Thanks.

-- 
tejun
--
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/