public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	Heiko Stuebner <heiko@sntech.de>,
	Doug Anderson <dianders@chromium.org>,
	Brian Norris <briannorris@chromium.org>,
	Wenrui Li <wenrui.li@rock-chips.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] Documentation: bindings: add dt documentation for Rockchip PCIe PHY
Date: Fri, 29 Jul 2016 16:34:35 -0500	[thread overview]
Message-ID: <20160729213435.GA15549@rob-hp-laptop> (raw)
In-Reply-To: <1469755326-10263-1-git-send-email-shawn.lin@rock-chips.com>

On Fri, Jul 29, 2016 at 09:22:05AM +0800, Shawn Lin wrote:
> This patch adds a binding that describes the Rockchip PCIe PHY
> found on Rockchip SoCs PCIe interface.
> 
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> 
> ---
> 
> Changes in v4: None
> Changes in v3:
> - rename the node to pcie_phy: pcie-phy suggested by Doug
> 
> Changes in v2:
> - add clk and reset description
> - remove unit-address
> 
>  .../devicetree/bindings/phy/rockchip-pcie-phy.txt  | 32 ++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/rockchip-pcie-phy.txt

Please add acks when posting new versions.

Rob

  parent reply	other threads:[~2016-07-29 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  1:22 [PATCH v4 1/2] Documentation: bindings: add dt documentation for Rockchip PCIe PHY Shawn Lin
2016-07-29  1:22 ` [PATCH v4 2/2] phy: add a driver for the Rockchip SoC internal " Shawn Lin
2016-08-17  8:12   ` Shawn Lin
2016-08-19 13:35   ` Kishon Vijay Abraham I
2016-07-29 21:34 ` Rob Herring [this message]
2016-08-01  3:03   ` [PATCH v4 1/2] Documentation: bindings: add dt documentation for Rockchip " Shawn 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=20160729213435.GA15549@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=briannorris@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=wenrui.li@rock-chips.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