Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "chunzhi.lin" <linchunzhi0@gmail.com>
Cc: netdev@vger.kernel.org, Frank.Sae@motor-comm.com,
	hkallweit1@gmail.com, linux@armlinux.org.uk, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
	linux-acpi@vger.kernel.org, rafael@kernel.org, lenb@kernel.org
Subject: Re: [PATCH 2/2] docs: acpi: dsd: add Motorcomm yt8xxx PHY properties
Date: Wed, 6 May 2026 14:20:32 +0200	[thread overview]
Message-ID: <d24c2a38-ec63-4973-91c8-357853d837b3@lunn.ch> (raw)
In-Reply-To: <20260506021813.3658669-3-linchunzhi0@gmail.com>

> diff --git a/Documentation/firmware-guide/acpi/index.rst b/Documentation/firmware-guide/acpi/index.rst
> index b246902f523f..3cd38bb4de15 100644
> --- a/Documentation/firmware-guide/acpi/index.rst
> +++ b/Documentation/firmware-guide/acpi/index.rst
> @@ -12,6 +12,7 @@ ACPI Support
>     dsd/data-node-references
>     dsd/leds
>     dsd/phy
> +   dsd/motorcomm-yt8xxx-phy
>     enumeration
>     osi

Please keep this sorted within dsd/. Yes, graph is in the wrong place,
but lets not make it worse.

Apart from that, this looks good.

    Andrew

---
pw-bot: cr

      reply	other threads:[~2026-05-06 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  2:18 [PATCH net-next 0/2] net: phy: motorcomm: add ACPI _DSD property support chunzhi.lin
2026-05-06  2:18 ` [PATCH 1/2] net: phy: motorcomm: use device properties for firmware tuning chunzhi.lin
2026-05-06 12:18   ` Andrew Lunn
2026-05-06  2:18 ` [PATCH 2/2] docs: acpi: dsd: add Motorcomm yt8xxx PHY properties chunzhi.lin
2026-05-06 12:20   ` Andrew Lunn [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=d24c2a38-ec63-4973-91c8-357853d837b3@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Frank.Sae@motor-comm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linchunzhi0@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafael@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