From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 40HQrv6FBlzF1vP for ; Fri, 6 Apr 2018 13:57:51 +1000 (AEST) Message-ID: <1522987056.21446.226.camel@kernel.crashing.org> Subject: Re: [RESEND v2 3/4] doc/devicetree: Persistent memory region bindings From: Benjamin Herrenschmidt To: Dan Williams , Oliver Cc: linux-nvdimm , linuxppc-dev , Device Tree Date: Fri, 06 Apr 2018 13:57:36 +1000 In-Reply-To: References: <20180403142415.30083-1-oohall@gmail.com> <20180403142415.30083-3-oohall@gmail.com> <20180404220750.0436bbe1@gmail.com> <87bmexua3s.fsf@concordia.ellerman.id.au> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.