linux-kernel - Re: [PATCH 1/3] x86, intel: Output microcode revision v5

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: <20111012084523.GB27853@elte.hu>
Date:	Wed, 12 Oct 2011 10:45:25 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, hpa@...or.com, tglx@...utronix.de,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 1/3] x86, intel: Output microcode revision v5

* Andi Kleen <andi@...stfloor.org> wrote:

> On Mon, Oct 10, 2011 at 09:00:44AM +0200, Ingo Molnar wrote:
> > 
> > Andi,
> > 
> > If you want me to apply these patches then they need to be reviewed 
> > and signed off by someone else who i trust and who i'm taking patches 
> > from.
> 
> Ingo,
> 
> There's noone else to sign off because noone else is writing the 
> patches.

The typical way of how such maintainer requests are solved is that 
you'll have to find someone who is willing and able to work with you 
on this topic, and who is willing to forward your patches to me or to 
the other x86 maintainers (or any of the submaintainers we pull 
from). It's not hard, we get and accept a lot of indirect patches.

Arguably i've already invested more time into this than i should 
have, this direct approach clearly does not work and i cannot trust 
you.

Thanks,

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