From: Markus Heidelberg Date: Fri, 26 Sep 2025 13:15:20 +0000 (+0200) Subject: docs: networking: phy: clarify abbreviation "PAL" X-Git-Tag: v6.18-rc1~132^2~33 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=29be241d11748dbcd9981587a85afa734942c885;p=thirdparty%2Flinux.git 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 Reviewed-by: Andrew Lunn Link: https://patch.msgid.link/20250926131520.222346-1-m.heidelberg@cab.de Signed-off-by: Jakub Kicinski --- diff --git a/Documentation/networking/phy.rst b/Documentation/networking/phy.rst index 7f159043ad5a9..b0f2ef83735da 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