Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753306AbbBYKWr (ORCPT <rfc822;w@1wt.eu>);
	Wed, 25 Feb 2015 05:22:47 -0500
Received: from mail-we0-f170.google.com ([74.125.82.170]:42579 "EHLO
	mail-we0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751023AbbBYKWp (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 25 Feb 2015 05:22:45 -0500
Date: Wed, 25 Feb 2015 11:22:40 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: 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>,
        Dan Williams <dan.j.williams@intel.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>,
        Matthew Wilcox <willy@linux.intel.com>,
        Andy Lutomirski <luto@amacapital.net>,
        Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/3 v2] e820: Fix handling of NvDIMM chips
Message-ID: <20150225102240.GC7134@gmail.com>
References: <54EB1D33.3050107@plexistor.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54EB1D33.3050107@plexistor.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1047
Lines: 33


* Boaz Harrosh <boaz@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 (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.

Thanks,

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