Message-ID: <54E5BB21.6040105@plexistor.com>
Date: Thu, 19 Feb 2015 12:29:53 +0200
From: Boaz Harrosh <boaz@plexistor.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ingo Molnar <mingo@kernel.org>, Dan Williams <dan.j.williams@intel.com>
CC: Christoph Hellwig <hch@infradead.org>,
        Matthew Wilcox <willy@linux.intel.com>, Ingo Molnar <mingo@redhat.com>,
        Ross Zwisler <ross.zwisler@linux.intel.com>, x86@kernel.org,
        linux-kernel <linux-kernel@vger.kernel.org>,
        "Roger C. Pao" <rcpao.enmotus@gmail.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        linux-nvdimm <linux-nvdimm@ml01.01.org>,
        "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips
References: <54E1CF5B.9020905@plexistor.com> <20150216220302.GF3364@wil.cx> <54E2FEF2.8060701@plexistor.com> <CAPcyv4if=9Cv__4D0oE9ds1C37TRDkURSVtyB8_k9Nc3WUwbrg@mail.gmail.com> <20150219004731.GA5477@infradead.org> <CAPcyv4jaqqgvjQC+QKvUohM7mAXAsZKbKntCEaiTozCCqwmFyA@mail.gmail.com> <20150219100151.GA591@gmail.com>
In-Reply-To: <20150219100151.GA591@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1546
Lines: 45

On 02/19/2015 12:01 PM, Ingo Molnar wrote:
> 
> * Dan Williams <dan.j.williams@intel.com> wrote:
> 
>> On Wed, Feb 18, 2015 at 4:47 PM, Christoph Hellwig <hch@infradead.org> wrote:
>>> On Wed, Feb 18, 2015 at 10:15:32AM -0800, Dan Williams wrote:
>>>> In fact it was originally "type-6" until ACPI 5 
>>>> claimed that number for official use, so these 
>>>> platforms, with early proof-of-concept nvdimm support, 
>>>> have already gone through one transition to a new 
>>>> number.  They need to do the same once an official 
>>>> number for nvdimm support is published.
>>>>
>>>> Put another way, these early platforms are already 
>>>> using out-of-tree patches for nvdimm enabling.  They 
>>>> can continue to do so, or switch to standard methods 
>>>> when the standard is published.
>>>
>>> Not supporting hardware that is widely avaiable (I have 
>>> some, too) is not very user friendly.
>>
>> Yes, as I agreed with Ingo, allowing a driver to assume 
>> control of an unknown memory type with a warning or a 
>> kernel taint seems fine.
> 
> If someone cooks up such a patch I can apply it.
> 
> Thanks,
> 
> 	Ingo
> 

I will submit a new version of my patch-1 with the pr_warn.

Or did you already apply my patch-1 and you want one on top?
What is the URL of your tree please?

Thanks
Boaz

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/