linux-kernel - Re: [PATCH 2/3] x86: add a is_e820

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: <20150326102810.GB19907@gmail.com>
Date:	Thu, 26 Mar 2015 11:28:10 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Christoph Hellwig <hch@....de>
Cc:	linux-nvdimm@...1.01.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	ross.zwisler@...ux.intel.com, axboe@...nel.dk, boaz@...xistor.com
Subject: Re: [PATCH 2/3] x86: add a is_e820_ram() helper


* Christoph Hellwig <hch@....de> wrote:

> On Thu, Mar 26, 2015 at 11:04:13AM +0100, Ingo Molnar wrote:
> > Yeah, the code is much clearer now:
> > 
> >   Acked-by: Ingo Molnar <mingo@...nel.org>
> > 
> > What tree is this intended for? Should I pick up the x86 bits?
> 
> The x86 bits really need to go through the x86 tree.  The pmem 
> driver itself would normally go through the block tree, but if Jens 
> is fine with it sending it through the x86 tree as well would allow 
> us to have a single complete tree for testing.

btw., there's half a dozen block drivers in arch/* platform code, so 
in theory even the block driver could be merged there - but I agree 
that it's much cleaner and more generic in drivers/block/.

Jens?

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/