tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
Documentation: ieee802154: fix grammar
Fix grammar where it improves readability.
Signed-off-by: Leo Stone <leocstone@gmail.com>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Link: https://lore.kernel.org/20241023041203.35313-1-leocstone@gmail.com
Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>
authored by
Leo Stone
and committed by
Stefan Schmidt
aad4b41a
b8ee7a11
+9
-7
+9
-7
Documentation/networking/ieee802154.rst
+9
-7
Documentation/networking/ieee802154.rst
···
72
72
possibly with some kinds of acceleration like automatic CRC computation and
73
73
comparison, automagic ACK handling, address matching, etc.
74
74
75
-
Those types of devices require different approach to be hooked into Linux kernel.
75
+
Each type of device requires a different approach to be hooked into the Linux
76
+
kernel.
76
77
77
78
HardMAC
78
79
-------
···
82
81
net_device, with .type = ARPHRD_IEEE802154. Data is exchanged with socket family
83
82
code via plain sk_buffs. On skb reception skb->cb must contain additional
84
83
info as described in the struct ieee802154_mac_cb. During packet transmission
85
-
the skb->cb is used to provide additional data to device's header_ops->create
86
-
function. Be aware that this data can be overridden later (when socket code
87
-
submits skb to qdisc), so if you need something from that cb later, you should
88
-
store info in the skb->data on your own.
84
+
the skb->cb is used to provide additional data to the device's
85
+
header_ops->create function. Be aware that this data can be overridden later
86
+
(when socket code submits skb to qdisc), so if you need something from that cb
87
+
later, you should store info in the skb->data on your own.
89
88
90
89
To hook the MLME interface you have to populate the ml_priv field of your
91
90
net_device with a pointer to struct ieee802154_mlme_ops instance. The fields
···
95
94
SoftMAC
96
95
-------
97
96
98
-
The MAC is the middle layer in the IEEE 802.15.4 Linux stack. This moment it
99
-
provides interface for drivers registration and management of slave interfaces.
97
+
The MAC is the middle layer in the IEEE 802.15.4 Linux stack. At the moment, it
98
+
provides an interface for driver registration and management of slave
99
+
interfaces.
100
100
101
101
NOTE: Currently the only monitor device type is supported - it's IEEE 802.15.4
102
102
stack interface for network sniffers (e.g. WireShark).