From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Michael Walle <michael@walle.cc>, Mark Brown <broonie@kernel.org>
Cc: Manohar.Puri@microchip.com, UNGLinuxDriver@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@microchip.com,
devicetree@vger.kernel.org, kavyasree.kotagiri@microchip.com,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
nicolas.ferre@microchip.com, robh+dt@kernel.org,
tudor.ambarus@microchip.com
Subject: Re: [PATCH] spi: atmel,quadspi: Define lan966x QSPI
Date: Thu, 7 Apr 2022 14:04:24 +0200 [thread overview]
Message-ID: <65a57655-2311-0f9d-8667-851755aaec1f@linaro.org> (raw)
In-Reply-To: <561bbc1cf43c3795eee67e10537ba365@walle.cc>
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
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Michael Walle <michael@walle.cc>, Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
tudor.ambarus@microchip.com, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, robh+dt@kernel.org,
kavyasree.kotagiri@microchip.com, Manohar.Puri@microchip.com,
krzk+dt@kernel.org, linux-spi@vger.kernel.org,
claudiu.beznea@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] spi: atmel,quadspi: Define lan966x QSPI
Date: Thu, 7 Apr 2022 14:04:24 +0200 [thread overview]
Message-ID: <65a57655-2311-0f9d-8667-851755aaec1f@linaro.org> (raw)
In-Reply-To: <561bbc1cf43c3795eee67e10537ba365@walle.cc>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-07 12:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 10:54 [PATCH] spi: atmel,quadspi: Define lan966x QSPI Kavyasree Kotagiri
2022-04-07 10:54 ` Kavyasree Kotagiri
2022-04-07 11:02 ` Mark Brown
2022-04-07 11:02 ` Mark Brown
2022-04-07 11:23 ` Michael Walle
2022-04-07 11:23 ` Michael Walle
2022-04-07 11:31 ` Mark Brown
2022-04-07 11:31 ` Mark Brown
2022-04-07 11:41 ` Michael Walle
2022-04-07 11:41 ` Michael Walle
2022-04-07 12:04 ` Krzysztof Kozlowski [this message]
2022-04-07 12:04 ` Krzysztof Kozlowski
2022-04-07 12:05 ` Krzysztof Kozlowski
2022-04-07 12:05 ` Krzysztof Kozlowski
2022-04-07 12:54 ` Tudor.Ambarus
2022-04-07 12:54 ` Tudor.Ambarus
2022-04-08 11:52 ` Kavyasree.Kotagiri
2022-04-08 11:52 ` Kavyasree.Kotagiri
2022-04-11 14:46 ` Michael Walle
2022-04-11 14:46 ` Michael Walle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65a57655-2311-0f9d-8667-851755aaec1f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tudor.ambarus@microchip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.