From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jack Zhu <jack.zhu@starfivetech.com>,
Minda Chen <minda.chen@starfivetech.com>,
"Vinod Koul" <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
<linux-phy@lists.infradead.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct file entry in STARFIVE JH7110 DPHY RX DRIVER
Date: Tue, 1 Aug 2023 09:21:35 +0800 [thread overview]
Message-ID: <c03886ed-f39e-09c4-6435-7a0e63341da7@starfivetech.com> (raw)
In-Reply-To: <20230731114856.14401-1-lukas.bulwahn@gmail.com>
On 2023/7/31 19:48, Lukas Bulwahn wrote:
> Commit f8aa660841bc ("phy: starfive: Add mipi dphy rx support") adds the
> MAINTAINERS section STARFIVE JH7110 DPHY RX DRIVER referring to
> 'phy-starfive-dphy-rx.c', but the file actually added in this commit is
> named 'phy-jh7110-dphy-rx.c'.
>
> Correct the file entry in STARFIVE JH7110 DPHY RX DRIVER.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Thank you for your correcting.
Reviewed-by: Changhuang Liang <changhuang.liang@starfivetech.com>
Thanks,
Changhuang
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 733bcfa0209a..003b0461641a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -20345,7 +20345,7 @@ M: Jack Zhu <jack.zhu@starfivetech.com>
> M: Changhuang Liang <changhuang.liang@starfivetech.com>
> S: Supported
> F: Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-rx.yaml
> -F: drivers/phy/starfive/phy-starfive-dphy-rx.c
> +F: drivers/phy/starfive/phy-jh7110-dphy-rx.c
>
> STARFIVE JH7110 MMC/SD/SDIO DRIVER
> M: William Qiu <william.qiu@starfivetech.com>
next prev parent reply other threads:[~2023-08-01 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:48 Lukas Bulwahn
2023-08-01 1:21 ` Changhuang Liang [this message]
2023-08-11 8:30 ` 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=c03886ed-f39e-09c4-6435-7a0e63341da7@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=jack.zhu@starfivetech.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lukas.bulwahn@gmail.com \
--cc=minda.chen@starfivetech.com \
--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
all inboxes | Powered by JetHome®