[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65a57655-2311-0f9d-8667-851755aaec1f@linaro.org>
Date: Thu, 7 Apr 2022 14:04:24 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Michael Walle <michael@...le.cc>, Mark Brown <broonie@...nel.org>
Cc: Manohar.Puri@...rochip.com, UNGLinuxDriver@...rochip.com,
alexandre.belloni@...tlin.com, claudiu.beznea@...rochip.com,
devicetree@...r.kernel.org, kavyasree.kotagiri@...rochip.com,
krzk+dt@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
nicolas.ferre@...rochip.com, robh+dt@...nel.org,
tudor.ambarus@...rochip.com
Subject: Re: [PATCH] spi: atmel,quadspi: Define lan966x QSPI
On 07/04/2022 13:41, Michael Walle wrote:
> Am 2022-04-07 13:31, schrieb Mark Brown:
>> On Thu, Apr 07, 2022 at 01:23:45PM +0200, Michael Walle wrote:
>>> The subject should also be prefixed with "dt-bindings: ".
>>
>> I tend to complain about people doing that.
>
> After all it is mentioned to use that prefix in
> Documentation/devicetree/bindings/submitting-patches.rst. I try to
> remember when submitting SPI related bindings.
>From my point of view, the dt-bindings prefix is still expected, just
after "spi:" (and other Marks' subsystems), because that's I am
filtering the bindings.
Your submissions had the prefix in wrong place, this one patch does not
have it all. :(
Best regards,
Krzysztof
Powered by blists - more mailing lists