devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Vinod Koul <vkoul@kernel.org>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH v2 1/2] devicetree: phy: rockchip-emmc optional add vendor prefix
Date: Tue, 15 Dec 2020 12:18:05 -0600	[thread overview]
Message-ID: <20201215181805.GA4145251@robh.at.kernel.org> (raw)
In-Reply-To: <20201215014409.905-2-chris.ruehl@gtsys.com.hk>

On Tue, 15 Dec 2020 09:44:07 +0800, Chris Ruehl wrote:
> Update the documentation and add the vendor prefix to the optional
> properties referred in vendor-prefixes.yaml.
> Follow up with
> commit 8b5c2b45b8f0a ("phy: rockchip: set pulldown for strobe line in dts")
> commit a8cef928276bb ("phy: rockchip-emmc: output tap delay dt property")

These could be Fixes tags.

> 
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
> ---
>  .../devicetree/bindings/phy/rockchip-emmc-phy.txt      | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

TBC, this needs to be applied for v5.11.

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

  reply	other threads:[~2020-12-15 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15  1:44 [PATCH v2 0/2] rockchip: emmc: rk3399 add vendor prefix Chris Ruehl
2020-12-15  1:44 ` [PATCH v2 1/2] devicetree: phy: rockchip-emmc optional " Chris Ruehl
2020-12-15 18:18   ` Rob Herring [this message]
2020-12-15  1:44 ` [PATCH v2 2/2] phy: rockchip: emmc, add vendor prefix to dts properties Chris Ruehl
2021-01-13 11:54 ` [PATCH v2 0/2] rockchip: emmc: rk3399 add vendor prefix Vinod Koul

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=20201215181805.GA4145251@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=chris.ruehl@gtsys.com.hk \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@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).