From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Karan Sanghavi <karansanghvi98@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] dt-bindings: spi: Add bcm2835-aux-spi.yaml file.
Date: Mon, 14 Oct 2024 19:57:58 +0200 [thread overview]
Message-ID: <09826ffb-b7d1-4244-af0d-854f1f0339a1@linaro.org> (raw)
In-Reply-To: <Zw1Oj1utiBJ9Sosg@Emma>
On 14/10/2024 19:02, Karan Sanghavi wrote:
> Converted the brcm,bcm2835-aux-spi.txt file to
> its respective yaml file format.
>
> Signed-off-by: Karan Sanghavi <karansanghvi98@gmail.com>
> ---
>
You already posted it and received review. Why do you send the same?
Please respond to the review.
See submitting-patches document.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-14 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 17:02 [PATCH] dt-bindings: spi: Add bcm2835-aux-spi.yaml file Karan Sanghavi
2024-10-14 17:57 ` Krzysztof Kozlowski [this message]
2024-10-15 18:09 ` [PATCH v2] dt-bindings: spi: Convert bcm2835-aux-spi.txt to Karan Sanghavi
2024-10-15 20:25 ` Conor Dooley
2024-10-16 10:13 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2024-09-29 7:22 [PATCH] dt-bindings: spi: Add bcm2835-aux-spi.yaml file Karan Sanghavi
2024-09-29 19:54 ` Krzysztof Kozlowski
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=09826ffb-b7d1-4244-af0d-854f1f0339a1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=karansanghvi98@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=skhan@linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).