From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Dege <michael.dege@renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/9] Doc: devicetree: bindings: rename r8a779f0-ether-serdes.yaml
Date: Fri, 9 May 2025 14:59:46 +0200 [thread overview]
Message-ID: <03d241b8-a5de-4cee-a761-d866dfee61da@kernel.org> (raw)
In-Reply-To: <TYRPR01MB14284C8E8145635A1AD8314F4828AA@TYRPR01MB14284.jpnprd01.prod.outlook.com>
On 09/05/2025 13:58, Michael Dege wrote:
> From 17e2e2044613eb2e738fadfe2b776593759a3994 Mon Sep 17 00:00:00 2001
> From: Michael Dege <michael.dege@renesas.com>
> Date: Fri, 9 May 2025 12:29:58 +0200
> Subject: [PATCH 2/9] Doc: devicetree: bindings: rename r8a779f0-ether-serdes.yaml
>
> The updated serdes driver supports multiple devices. The original name included the device code of a single device. The new name is more generic.
>
> Signed-off-by: Michael Dege <michael.dege@renesas.com>
> ---
> ...a779f0-ether-serdes.yaml => renesas,renesas-ether-serdes.yaml} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-) rename Documentation/devicetree/bindings/phy/{renesas,r8a779f0-ether-serdes.yaml => renesas,renesas-ether-serdes.yaml} (100%)
>
> diff --git a/Documentation/devicetree/bindings/phy/renesas,r8a779f0-ether-serdes.yaml b/Documentation/devicetree/bindings/phy/renesas,renesas-ether-serdes.yaml
> similarity index 100%
> rename from Documentation/devicetree/bindings/phy/renesas,r8a779f0-ether-serdes.yaml
> rename to Documentation/devicetree/bindings/phy/renesas,renesas-ether-serdes.yaml
Obviously NAK for all the same reasons plus this makes no sense. Don't
send this again, even after fixing the rest.
> --
> 2.34.1
>
> ________________________________
>
> Renesas Electronics Europe GmbH
> Registered Office: Arcadiastrasse 10
> DE-40472 Duesseldorf
> Commercial Registry: Duesseldorf, HRB 3708
> Managing Director: Carsten Jauch
> VAT-No.: DE 14978647
> Tax-ID-No: 105/5839/1793
>
> Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and contains proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-05-09 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 11:55 Doc: devicetree: bindings: rename r8a779f0-ether-serdes.yaml Michael Dege
2025-05-09 11:58 ` [PATCH 2/9] " Michael Dege
2025-05-09 12:59 ` Krzysztof Kozlowski [this message]
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=03d241b8-a5de-4cee-a761-d866dfee61da@kernel.org \
--to=krzk@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michael.dege@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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