linux-kernel - Re: [PATCH 0/3 v2] e820: Fix handling of NvDIMM chips

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:	Wed, 25 Feb 2015 16:42:14 +0200
From:	Boaz Harrosh <boaz@...xistor.com>
To:	Ingo Molnar <mingo@...nel.org>
CC:	Ingo Molnar <mingo@...hat.com>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>, x86@...nel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Roger C. Pao" <rcpao.enmotus@...il.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-nvdimm <linux-nvdimm@...ts.01.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Matthew Wilcox <willy@...ux.intel.com>,
	Andy Lutomirski <luto@...capital.net>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH 0/3 v2] e820: Fix handling of NvDIMM chips

On 02/25/2015 12:22 PM, Ingo Molnar wrote:
> 
> * Boaz Harrosh <boaz@...xistor.com> wrote:
> 
>> List of patches:
>>  [PATCH 1/3] e820: Don't let unknown DIMM type come out BUSY
>> 	The main fix
>>
>>  [PATCH 2/3] resource: Add new flag IORESOURCE_WARN (64bit)
>> 	Warn in request_resource
>>
>>  [PATCH 3A/3] e820: Add the unknown-12 Memory type (DDR3-NvDIMM)
>> 	Please accept this simple patch
>>
>>  [PATCH 3B/3] e820: dynamic unknown-xxx names (for DDR3-NvDIMM)
>> 	Else we need this crap
> 
> Please also include your nvdimm driver in your next 
> submission (even if that is not part of the submission 
> yet), so that we can see how the driver makes use of the 
> new facility.
> 
> There's quite a bit of confusion about what means what, 
> people are not of one opinion, and it's easier to see and 
> check the fine code instead of making assumptions.
> 

Hi Ingo

Sure, I will send it as RFC as part of the next send.
Ingo, did we please decide on the [PATCH 3A/3]?

> Thanks,
> 
> 	Ingo
> 

Thanks very much
Boaz

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