[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251016092552.27053-1-bagasdotme@gmail.com>
Date: Thu, 16 Oct 2025 16:25:52 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Documentation <linux-doc@...r.kernel.org>,
Linux Networking <netdev@...r.kernel.org>
Cc: Subash Abhinov Kasiviswanathan <subash.a.kasiviswanathan@....qualcomm.com>,
Sean Tranchetti <sean.tranchetti@....qualcomm.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
Jonathan Corbet <corbet@....net>,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH net-next] net: rmnet: Use section heading for packet format subsections
Format subsections of "Packet format" section as reST subsections.
Link: https://lore.kernel.org/linux-doc/aO_MefPIlQQrCU3j@horms.kernel.org/
Suggested-by: Simon Horman <horms@...nel.org>
Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
---
.../cellular/qualcomm/rmnet.rst | 20 +++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/Documentation/networking/device_drivers/cellular/qualcomm/rmnet.rst b/Documentation/networking/device_drivers/cellular/qualcomm/rmnet.rst
index 289c146a829153..1115606496b67d 100644
--- a/Documentation/networking/device_drivers/cellular/qualcomm/rmnet.rst
+++ b/Documentation/networking/device_drivers/cellular/qualcomm/rmnet.rst
@@ -27,7 +27,8 @@ these MAP frames and send them to appropriate PDN's.
2. Packet format
================
-a. MAP packet v1 (data / control)
+A. MAP packet v1 (data / control)
+---------------------------------
MAP header fields are in big endian format.
@@ -53,7 +54,8 @@ Multiplexer ID is to indicate the PDN on which data has to be sent.
Payload length includes the padding length but does not include MAP header
length.
-b. Map packet v4 (data / control)
+B. MAP packet v4 (data / control)
+---------------------------------
MAP header fields are in big endian format.
@@ -106,7 +108,8 @@ over which checksum is computed.
Checksum value, indicates the checksum computed.
-c. MAP packet v5 (data / control)
+C. MAP packet v5 (data / control)
+---------------------------------
MAP header fields are in big endian format.
@@ -133,7 +136,8 @@ Multiplexer ID is to indicate the PDN on which data has to be sent.
Payload length includes the padding length but does not include MAP header
length.
-d. Checksum offload header v5
+D. Checksum offload header v5
+-----------------------------
Checksum offload header fields are in big endian format.
@@ -154,7 +158,10 @@ indicates that the calculated packet checksum is invalid.
Reserved bits must be zero when sent and ignored when received.
-e. MAP packet v1/v5 (command specific)::
+E. MAP packet v1/v5 (command specific)
+--------------------------------------
+
+Packet format::
Bit 0 1 2-7 8 - 15 16 - 31
Function Command Reserved Pad Multiplexer ID Payload length
@@ -176,7 +183,8 @@ Command types
3 is for error during processing of commands
= ==========================================
-f. Aggregation
+F. Aggregation
+--------------
Aggregation is multiple MAP packets (can be data or command) delivered to
rmnet in a single linear skb. rmnet will process the individual
base-commit: cb85ca4c0a349e246cd35161088aa3689ae5c580
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists