From: Beiyan Yun <root@infi.wang>
To: u-boot@lists.denx.de
Cc: Beiyan Yun <root@infi.wang>, Tom Rini <trini@konsulko.com>
Subject: [PATCH RESEND 2/4] doc: bindings: fix aquantia-phy.txt typo
Date: Tue, 23 Sep 2025 15:12:59 +0800 [thread overview]
Message-ID: <20250923071315.276114-3-root@infi.wang> (raw)
In-Reply-To: <20250923071315.276114-1-root@infi.wang>
Fix typo: "weays" -> "ways"
Signed-off-by: Beiyan Yun <root@infi.wang>
---
doc/device-tree-bindings/net/aquantia-phy.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/device-tree-bindings/net/aquantia-phy.txt b/doc/device-tree-bindings/net/aquantia-phy.txt
index 89ce61e05bb..7dd3d45df12 100644
--- a/doc/device-tree-bindings/net/aquantia-phy.txt
+++ b/doc/device-tree-bindings/net/aquantia-phy.txt
@@ -4,7 +4,7 @@ This text describes properties that are applicable to Aquantia PHY nodes in
addition to the bindings in phy.txt.
Aquantia PHYs allow some flexibility in the way they are wired in a system,
-they allow MDI pins to be reversed, LEDs linked up in different weays, have an
+they allow MDI pins to be reversed, LEDs linked up in different ways, have an
I2C slave interface that can be used for debug. Normally the configuration
corresponding to these is driven by the PHY firmware with the downside that
a custom firmware is needed for each integration of a PHY.
--
2.47.3
next prev parent reply other threads:[~2025-09-23 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 7:12 [PATCH RESEND 0/4] net: phy: aquantia: Switch to generic firmware loader Beiyan Yun
2025-09-23 7:12 ` [PATCH RESEND 1/4] net: phy: aquantia: switch to use phy_get_ofnode() Beiyan Yun
2025-09-23 7:12 ` Beiyan Yun [this message]
2025-09-23 7:13 ` [PATCH RESEND 3/4] net: phy: aquantia: use generic firmware loader Beiyan Yun
2025-09-23 7:13 ` [PATCH RESEND 4/4] doc: bindings: add Aquantia PHY node's "firmware-name" binding Beiyan Yun
2025-09-23 12:44 ` Yao Zi
2025-09-26 8:22 ` Beiyan Yun
2025-09-26 9:30 ` Beiyan Yun
2025-09-28 13:04 ` Yao Zi
2025-09-29 20:55 ` Tom Rini
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=20250923071315.276114-3-root@infi.wang \
--to=root@infi.wang \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.