linux-kernel - Re: [patch] x86, voyager: fix ioremap

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]

Date:	Mon, 28 Apr 2008 09:55:53 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Christoph Hellwig <hch@...radead.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [patch] x86, voyager: fix ioremap_nocache()

Christoph Hellwig wrote:
> On Mon, Apr 28, 2008 at 01:18:09AM +0200, Ingo Molnar wrote:
>> ... but the PAT patchset was all around lkml. The ioremap change was 
>> trivial, went into v2.6.25 and was discussed on lkml:
>>
>>   http://lkml.org/lkml/2008/1/25/287
> 
> lkml is a hell-hole with a signal/noise ratio worse than slashdot.  Any
> chance you could create a linux-x86 list for x86 specific changes so
> that a focussed review and discussion can happen?

We have been talking about it between us.  Originally, Ingo was opposed 
to it exactly *because* he wanted to keep the development as open as 
possible.  After the merge window craziness is over, we may want to 
revisit this.

I'm not saying we're doing everything right at the moment; heck, we're 
still figuring out how to work this on three people.  However, I want to 
set the record straight - Ingo *especially* has been concerned to keep 
development open from the very beginning.

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