[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250926131520.222346-1-m.heidelberg@cab.de>
Date: Fri, 26 Sep 2025 15:15:20 +0200
From: Markus Heidelberg <m.heidelberg@....de>
To: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>
CC: Russell King <linux@...linux.org.uk>, <netdev@...r.kernel.org>,
<linux-doc@...r.kernel.org>, Markus Heidelberg <m.heidelberg@....de>
Subject: [PATCH] docs: networking: phy: clarify abbreviation "PAL"
It is suddenly used in the text without introduction, so the meaning
might have been unclear to readers.
Signed-off-by: Markus Heidelberg <m.heidelberg@....de>
---
Documentation/networking/phy.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/networking/phy.rst b/Documentation/networking/phy.rst
index 7f159043ad5a..b0f2ef83735d 100644
--- a/Documentation/networking/phy.rst
+++ b/Documentation/networking/phy.rst
@@ -20,7 +20,7 @@ sometimes quite different) ethernet controllers connected to the same
management bus, it is difficult to ensure safe use of the bus.
Since the PHYs are devices, and the management busses through which they are
-accessed are, in fact, busses, the PHY Abstraction Layer treats them as such.
+accessed are, in fact, busses, the PHY Abstraction Layer (PAL) treats them as such.
In doing so, it has these goals:
#. Increase code-reuse
base-commit: 203e3beb73e53584ca90bc2a6d8240b9b12b9bcf
--
2.43.0
Powered by blists - more mailing lists