drivers/net/wireless/quantenna/qtnfmac/switchdev.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/quantenna/qtnfmac/switchdev.h

Extension

.h

Size

459 bytes

Lines

25

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/skbuff.h

Detected Declarations

• function qtnfmac_switch_mark_skb_flooded
• function qtnfmac_switch_mark_skb_flooded

Annotated Snippet

#ifndef QTNFMAC_SWITCHDEV_H_
#define QTNFMAC_SWITCHDEV_H_

#include <linux/skbuff.h>

#ifdef CONFIG_NET_SWITCHDEV

static inline void qtnfmac_switch_mark_skb_flooded(struct sk_buff *skb)
{
	skb->offload_fwd_mark = 1;
}

#else

static inline void qtnfmac_switch_mark_skb_flooded(struct sk_buff *skb)
{
}

#endif

#endif /* QTNFMAC_SWITCHDEV_H_ */

Annotation

• Immediate include surface: `linux/skbuff.h`.
• Detected declarations: `function qtnfmac_switch_mark_skb_flooded`, `function qtnfmac_switch_mark_skb_flooded`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.