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

2015-02-25 Thread Boaz Harrosh
On 02/25/2015 12:22 PM, Ingo Molnar wrote: > > * Boaz Harrosh 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]

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

2015-02-25 Thread Ingo Molnar
* Boaz Harrosh 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) >

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

2015-02-25 Thread Boaz Harrosh
On 02/25/2015 12:22 PM, Ingo Molnar wrote: * Boaz Harrosh b...@plexistor.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]

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

2015-02-25 Thread Ingo Molnar
* Boaz Harrosh b...@plexistor.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

[PATCH 0/3 v2] e820: Fix handling of NvDIMM chips

2015-02-23 Thread Boaz Harrosh
Hi [v2] * Added warning at bring up about unknown type * Added an extra patch to warn-print in request_resource * changed name from NvDIMM-12 => unknown-12 I wish we would reconsider this. So we need to suffer until some unknown future when ACPI decides to reuse type-12. When this happens we

[PATCH 0/3 v2] e820: Fix handling of NvDIMM chips

2015-02-23 Thread Boaz Harrosh
Hi [v2] * Added warning at bring up about unknown type * Added an extra patch to warn-print in request_resource * changed name from NvDIMM-12 = unknown-12 I wish we would reconsider this. So we need to suffer until some unknown future when ACPI decides to reuse type-12. When this happens we