From: Johan Jonker <jbx6244@gmail.com>
To: vkoul@kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, heiko@sntech.de,
linux-phy@lists.infradead.org, krzysztof.kozlowski+dt@linaro.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v1] dt-bindings: phy: rename phy-rockchip-inno-usb2.yaml
Date: Tue, 31 Jan 2023 11:39:46 +0100 [thread overview]
Message-ID: <8c33967b-1b91-42d2-879b-fa73dd8ecbeb@gmail.com> (raw)
In-Reply-To: <167320365145.195794.14991903357914132463.robh@kernel.org>
On 1/8/23 19:48, Rob Herring wrote:
>
> On Thu, 29 Dec 2022 12:39:17 +0100, Johan Jonker wrote:
>> Rename phy-rockchip-inno-usb2.yaml to a more common format of
>> rockchip,inno-usb2phy.yaml
>>
>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>> ---
>>
>> Apply after:
>> dt-bindings: soc: rockchip: grf: add rockchip,rk3288-dp-phy.yaml
Hi Vinod, Heiko,
This patch has been acked from the device tree side.
If it suits you is there Ack from the phy side possible, so that Heiko can merge it to grf.yaml in the order that he likes.
Johan
>> ---
>> .../{phy-rockchip-inno-usb2.yaml => rockchip,inno-usb2phy.yaml} | 2 +-
>> Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>> rename Documentation/devicetree/bindings/phy/{phy-rockchip-inno-usb2.yaml => rockchip,inno-usb2phy.yaml} (98%)
>>
>
> Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-01-31 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 11:39 [PATCH v1] dt-bindings: phy: rename phy-rockchip-inno-usb2.yaml Johan Jonker
2023-01-08 18:48 ` Rob Herring
2023-01-31 10:39 ` Johan Jonker [this message]
2023-01-31 10:59 ` Vinod Koul
2023-02-01 17:43 ` Heiko Stuebner
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=8c33967b-1b91-42d2-879b-fa73dd8ecbeb@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@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).