Commit a0aea57786fe9c6b62b1a4f28409582520fa494f
1 parent
3a5209e3b2
Exists in
master
and in
4 other branches
ieee802154: document the skb->cb usage clearly.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Showing 1 changed file with 7 additions and 2 deletions Side-by-side Diff
Documentation/networking/ieee802154.txt
| ... | ... | @@ -56,8 +56,12 @@ |
| 56 | 56 | |
| 57 | 57 | See the header include/net/ieee802154_netdev.h. You have to implement Linux |
| 58 | 58 | net_device, with .type = ARPHRD_IEEE802154. Data is exchanged with socket family |
| 59 | -code via plain sk_buffs. The control block of sk_buffs will contain additional | |
| 60 | -info as described in the struct ieee802154_mac_cb. | |
| 59 | +code via plain sk_buffs. On skb reception skb->cb must contain additional | |
| 60 | +info as described in the struct ieee802154_mac_cb. During packet transmission | |
| 61 | +the skb->cb is used to provide additional data to device's header_ops->create | |
| 62 | +function. Be aware, that this data can be overriden later (when socket code | |
| 63 | +submits skb to qdisc), so if you need something from that cb later, you should | |
| 64 | +store info in the skb->data on your own. | |
| 61 | 65 | |
| 62 | 66 | To hook the MLME interface you have to populate the ml_priv field of your |
| 63 | 67 | net_device with a pointer to struct ieee802154_mlme_ops instance. All fields are |