aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/x25.rst
diff options
context:
space:
mode:
authorXie He <xie.he.0141@gmail.com>2020-12-08 19:33:46 -0800
committerJakub Kicinski <kuba@kernel.org>2020-12-12 17:15:33 -0800
commit13458ffe0a953e17587f172a8e5059c243e6850a (patch)
tree93ea5e6f7b0463109485d871b22cc7d1e8a7d172 /Documentation/networking/x25.rst
parentinet: frags: batch fqdir destroy works (diff)
downloadlinux-dev-13458ffe0a953e17587f172a8e5059c243e6850a.tar.xz
linux-dev-13458ffe0a953e17587f172a8e5059c243e6850a.zip
net: x25: Remove unimplemented X.25-over-LLC code stubs
According to the X.25 documentation, there was a plan to implement X.25-over-802.2-LLC. It never finished but left various code stubs in the X.25 code. At this time it is unlikely that it would ever finish so it may be better to remove those code stubs. Also change the documentation to make it clear that this is not a ongoing plan anymore. Change words like "will" to "could", "would", etc. Cc: Martin Schiller <ms@dev.tdt.de> Signed-off-by: Xie He <xie.he.0141@gmail.com> Link: https://lore.kernel.org/r/20201209033346.83742-1-xie.he.0141@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'Documentation/networking/x25.rst')
-rw-r--r--Documentation/networking/x25.rst12
1 files changed, 5 insertions, 7 deletions
diff --git a/Documentation/networking/x25.rst b/Documentation/networking/x25.rst
index 00e45d384ba0..e11d9ebdf9a3 100644
--- a/Documentation/networking/x25.rst
+++ b/Documentation/networking/x25.rst
@@ -19,13 +19,11 @@ implementation of LAPB. Therefore the LAPB modules would be called by
unintelligent X.25 card drivers and not by intelligent ones, this would
provide a uniform device driver interface, and simplify configuration.
-To confuse matters a little, an 802.2 LLC implementation for Linux is being
-written which will allow X.25 to be run over an Ethernet (or Token Ring) and
-conform with the JNT "Pink Book", this will have a different interface to
-the Packet Layer but there will be no confusion since the class of device
-being served by the LLC will be completely separate from LAPB. The LLC
-implementation is being done as part of another protocol project (SNA) and
-by a different author.
+To confuse matters a little, an 802.2 LLC implementation is also possible
+which could allow X.25 to be run over an Ethernet (or Token Ring) and
+conform with the JNT "Pink Book", this would have a different interface to
+the Packet Layer but there would be no confusion since the class of device
+being served by the LLC would be completely separate from LAPB.
Just when you thought that it could not become more confusing, another
option appeared, XOT. This allows X.25 Packet Layer frames to operate over