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: <20101005193803.e805b3eb.sfr@canb.auug.org.au>
Date:	Tue, 5 Oct 2010 19:38:03 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Tejun Heo <tj@...nel.org>, 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

Hi Ingo,

On Tue, 5 Oct 2010 09:01:23 +0200 Ingo Molnar <mingo@...e.hu> wrote:
>
> Fortunately there's a really simple solution: wait for an explicit reply 
> from a maintainer before adding a new-feature tree. (Solicite again via 
> a To: email if the Cc: went unanswered by the maintainers.)

Sure we can try that.

> Could you please start using that method for all subsystems i 
> co-maintain?

So, to be clear, from the MAINTAINERS file that would be LOCKDEP AND
LOCKSTAT, PERFORMANCE EVENTS SUBSYSTEM, SCHEDULER, TRACING, and X86
ARCHITECTURE.  Any others?  If so could you please update the MAINTAINERS
file as (at my age) I am likely to forget and other may not guess.
Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped