linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Jon Lin <jon.lin@rock-chips.com>
Cc: Mark Brown <broonie@kernel.org>,
	"heiko@sntech.de" <heiko@sntech.de>,
	linux-spi <linux-spi@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v7 1/6] dt-bindings: spi: spi-rockchip: add description for rv1126
Date: Wed, 16 Jun 2021 09:26:23 -0600	[thread overview]
Message-ID: <CAL_JsqJWzECC_=xm6OnB63ofnTQC_4VZZO-mhkiTJDYx=93fcw@mail.gmail.com> (raw)
In-Reply-To: <20210615032620.24769-2-jon.lin@rock-chips.com>

On Mon, Jun 14, 2021 at 9:26 PM Jon Lin <jon.lin@rock-chips.com> wrote:
>
> The description below will be used for rv1126.dtsi or compatible one in
> the future
>
> Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
> ---
>
> Changes in v7:
> - Fall back "rockchip,rv1126-spi" to "rockchip,rk3066-spi"
>
> Changes in v6:
> - Consider to compatibility, the "rockchip,rk3568-spi" is removed in
>   Series-changes v5, so the commit massage should also remove the
>   corresponding information
>
> Changes in v5:
> - Change to leave one compatible id rv1126, and rk3568 is compatible
>   with rv1126
>
> Changes in v4:
> - Adjust the order patches
> - Simply commit massage like redundancy "application" content
>
> Changes in v3:
> - Fix compile error which is find by Sascha in [v2,2/8]
>
>  Documentation/devicetree/bindings/spi/spi-rockchip.yaml | 1 +
>  1 file changed, 1 insertion(+)

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-06-16 15:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 11:18 [PATCH v6 0/6] Support ROCKCHIP SPI new feature Jon Lin
2021-06-07 11:18 ` [PATCH v6 1/6] dt-bindings: spi: spi-rockchip: add description for rv1126 Jon Lin
2021-06-10 16:06   ` Rob Herring
2021-06-10 19:38     ` Johan Jonker
2021-06-07 11:18 ` [PATCH v6 2/6] spi: rockchip: add compatible string " Jon Lin
2021-06-07 11:18 ` [PATCH v6 3/6] spi: rockchip: Set rx_fifo interrupt waterline base on transfer item Jon Lin
2021-06-07 11:18 ` [PATCH v6 4/6] spi: rockchip: Wait for STB status in slave mode tx_xfer Jon Lin
2021-06-07 11:19 ` [PATCH v6 5/6] spi: rockchip: Support cs-gpio Jon Lin
2021-06-07 11:19   ` [PATCH v6 6/6] spi: rockchip: Support SPI_CS_HIGH Jon Lin
2021-06-15  3:26 ` [PATCH v7 0/6] Support ROCKCHIP SPI new feature Jon Lin
2021-06-15  3:26   ` [PATCH v7 1/6] dt-bindings: spi: spi-rockchip: add description for rv1126 Jon Lin
2021-06-16 15:26     ` Rob Herring [this message]
2021-06-15  3:26   ` [PATCH v7 2/6] spi: rockchip: add compatible string " Jon Lin
2021-06-15  3:26   ` [PATCH v7 3/6] spi: rockchip: Set rx_fifo interrupt waterline base on transfer item Jon Lin
2021-06-15  3:26   ` [PATCH v7 4/6] spi: rockchip: Wait for STB status in slave mode tx_xfer Jon Lin

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='CAL_JsqJWzECC_=xm6OnB63ofnTQC_4VZZO-mhkiTJDYx=93fcw@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jon.lin@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-spi@vger.kernel.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).