net/wireless/ethtool.c

File Facts

System

Linux kernel

Corpus path

net/wireless/ethtool.c

Extension

.c

Size

825 bytes

Lines

30

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/utsname.h
• net/cfg80211.h
• core.h
• rdev-ops.h

Detected Declarations

• function cfg80211_get_drvinfo
• export cfg80211_get_drvinfo

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
#include <linux/utsname.h>
#include <net/cfg80211.h>
#include "core.h"
#include "rdev-ops.h"

void cfg80211_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo *info)
{
	struct wireless_dev *wdev = dev->ieee80211_ptr;
	struct device *pdev = wiphy_dev(wdev->wiphy);

	if (pdev->driver)
		strscpy(info->driver, pdev->driver->name,
			sizeof(info->driver));
	else
		strscpy(info->driver, "N/A", sizeof(info->driver));

	strscpy(info->version, init_utsname()->release, sizeof(info->version));

	if (wdev->wiphy->fw_version[0])
		strscpy(info->fw_version, wdev->wiphy->fw_version,
			sizeof(info->fw_version));
	else
		strscpy(info->fw_version, "N/A", sizeof(info->fw_version));

	strscpy(info->bus_info, dev_name(pdev),
		sizeof(info->bus_info));
}
EXPORT_SYMBOL(cfg80211_get_drvinfo);

Annotation

• Immediate include surface: `linux/utsname.h`, `net/cfg80211.h`, `core.h`, `rdev-ops.h`.
• Detected declarations: `function cfg80211_get_drvinfo`, `export cfg80211_get_drvinfo`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.