From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<robh+dt@kernel.org>, <lukas@wunner.de>, <bbrezillon@kernel.org>,
<p.yadav@ti.com>, <linux-tegra@vger.kernel.org>,
<broonie@kernel.org>, <tudor.ambarus@microchip.com>,
<devicetree@vger.kernel.org>, <jonathanh@nvidia.com>,
<thierry.reding@gmail.com>
Subject: Re: [PATCH v5 2/9] dt-bindings: spi: Add Tegra Quad SPI device tree binding
Date: Mon, 4 Jan 2021 09:33:22 -0800 [thread overview]
Message-ID: <4ac13c7b-dcf1-0a7d-c573-83890cba6a67@nvidia.com> (raw)
In-Reply-To: <20201231183357.GA2112085@robh.at.kernel.org>
On 12/31/20 10:33 AM, Rob Herring wrote:
> On Mon, 21 Dec 2020 13:17:32 -0800, Sowjanya Komatineni wrote:
>> This patch adds YAML based device tree binding document for Tegra
>> Quad SPI driver.
>>
>> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
>> ---
>> .../bindings/spi/nvidia,tegra210-quad.yaml | 117 +++++++++++++++++++++
>> 1 file changed, 117 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra210-quad.yaml
>>
>
> Please add Acked-by/Reviewed-by tags when posting new versions. However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
>
> If a tag was not added on purpose, please state why and what changed.
>
Sorry Rob. Missed to add tag from v4 to v5.
Regards,
Sowjanya
next prev parent reply other threads:[~2021-01-04 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 21:17 [PATCH v5 0/9] Add Tegra Quad SPI driver Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 1/9] dt-bindings: clock: tegra: Add clock ID TEGRA210_CLK_QSPI_PM Sowjanya Komatineni
2021-01-26 10:03 ` Thierry Reding
2021-01-26 12:23 ` Mark Brown
2020-12-21 21:17 ` [PATCH v5 2/9] dt-bindings: spi: Add Tegra Quad SPI device tree binding Sowjanya Komatineni
2020-12-31 18:33 ` Rob Herring
2021-01-04 17:33 ` Sowjanya Komatineni [this message]
2020-12-21 21:17 ` [PATCH v5 3/9] MAINTAINERS: Add Tegra Quad SPI driver section Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 4/9] spi: tegra210-quad: Add support for Tegra210 QSPI controller Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 5/9] spi: spi-mem: Mark dummy transfers by setting dummy_data bit Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 6/9] spi: tegra210-quad: Add support for hardware dummy cycles transfer Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 7/9] arm64: tegra: Enable QSPI on Jetson Nano Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 8/9] arm64: tegra: Add QSPI nodes on Tegra194 Sowjanya Komatineni
2020-12-21 21:17 ` [PATCH v5 9/9] arm64: tegra: Enable QSPI on Jetson Xavier NX Sowjanya Komatineni
2021-01-06 14:59 ` (subset) [PATCH v5 0/9] Add Tegra Quad SPI driver Mark Brown
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=4ac13c7b-dcf1-0a7d-c573-83890cba6a67@nvidia.com \
--to=skomatineni@nvidia.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=p.yadav@ti.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--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 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).