[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6e1ef2eb-adb4-4341-f671-0d21fadda3e9@gmail.com>
Date: Mon, 8 Mar 2021 14:32:15 +0100
From: Rafał Miłecki <zajec5@...il.com>
To: Ansuel Smith <ansuelsmth@...il.com>
Cc: Richard Weinberger <richard@....at>, devicetree@...r.kernel.org,
Vignesh Raghavendra <vigneshr@...com>,
Boris Brezillon <bbrezillon@...nel.org>,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
linux-mtd@...ts.infradead.org,
Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: [PATCH v2 3/3] dt-bindings: mtd: Document use of nvmem-partitions
compatible
On 07.03.2021 18:04, Ansuel Smith wrote:
> On Mon, Mar 08, 2021 at 10:48:32AM +0100, Rafał Miłecki wrote:
>> On 16.02.2021 22:26, Ansuel Smith wrote:
>>> Document nvmem-partitions compatible used to treat mtd partitions as a
>>> nvmem provider.
>>
>> I'm just wondering if "nvmem-partitions" is accurate enough. Partitions
>> bit sounds a bit ambiguous in the mtd context.
>>
>> What do you think about "mtd-nvmem-cells" or just "nvmem-cells"?
>
> I read somewhere that mtd is not so standard so "nvmem-cells" should be the
> right compatible.
> To sum up, with v2 I should change the compatible name and just push the
> 2 and 3 patch. (waiting your fix to be accepted) Correct?
I'm also quite sure you're fine to send V2 now, if you just let
maintainers know (e.g. in a comment below a --- tear line) that it
depends on the:
[PATCH] mtd: parsers: ofpart: limit parsing of deprecated DT syntax
In other words: you don't need to wait for my patch to get accepted.
Powered by blists - more mailing lists