From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [RESEND v2 3/4] doc/devicetree: Persistent memory region bindings Date: Fri, 06 Apr 2018 13:57:36 +1000 Message-ID: <1522987056.21446.226.camel@kernel.crashing.org> References: <20180403142415.30083-1-oohall@gmail.com> <20180403142415.30083-3-oohall@gmail.com> <20180404220750.0436bbe1@gmail.com> <87bmexua3s.fsf@concordia.ellerman.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" To: Dan Williams , Oliver Cc: Device Tree , linuxppc-dev , linux-nvdimm List-Id: devicetree@vger.kernel.org On Thu, 2018-04-05 at 19:25 -0700, Dan Williams wrote: > > > Please also include my niggly nit picky trivial annoying bike shed > > > color for the driver name to *not* use the "nd_region" suffix for a > > > driver registering "nvdimm_bus" objects. "of_pmem_range" or > > > "of_pmem_bus" or almost anything else would be fine. > > > > Oh sure, would using of_pmem_region to match the compatible be ok? > > That works for me. The prefix "of" is not generally used in matching properties,... my own pot of paint :) Cheers, Ben.