[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <88740a95-d7b0-e5d0-62db-65b41c66c5bc@linaro.org>
Date: Wed, 7 Jun 2023 17:07:43 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Arseniy Krasnov <avkrasnov@...rdevices.ru>,
Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Liang Yang <liang.yang@...ogic.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Neil Armstrong <neil.armstrong@...aro.org>,
Kevin Hilman <khilman@...libre.com>,
Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
oxffffaa@...il.com, kernel@...rdevices.ru,
linux-mtd@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] dt-bindings: nand: meson: Fix 'nand-rb' property
On 07/06/2023 16:55, Arseniy Krasnov wrote:
>>>> The bindings and your driver internal representation are two different
>>>> things. Anyway, as mentioned above, wiring the RB line to one die and
>>>> not the other would be valid hardware design and would require the rb
>>>> property to be in the chip node. Please perform a per-chip property read
>>>> in the driver as well.
>>>
>>> Done, I resend both patches (bindings + driver update) as a single patchset. Your review comments
>>> for driver code were also fixed.
>>
>> No, please send new version, not the same. New version means with fixed
>> comments and with patch changelog.
>
> Sorry, Yes, I mean new version, here it is:
> https://lore.kernel.org/linux-mtd/20230607145026.2899547-1-AVKrasnov@sberdevices.ru/
>
> There I fixed bindings and tested it.
I still see v1 and there is no changelog. So it's the same?
Best regards,
Krzysztof
Powered by blists - more mailing lists