drivers/net/ethernet/intel/ice/ice_sf_vsi_vlan_ops.c
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/intel/ice/ice_sf_vsi_vlan_ops.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/intel/ice/ice_sf_vsi_vlan_ops.c- Extension
.c- Size
- 506 bytes
- Lines
- 22
- 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
ice_vsi_vlan_ops.hice_vsi_vlan_lib.hice_vlan_mode.hice.hice_sf_vsi_vlan_ops.h
Detected Declarations
function ice_sf_vsi_init_vlan_ops
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/* Copyright (c) 2023, Intel Corporation. */
#include "ice_vsi_vlan_ops.h"
#include "ice_vsi_vlan_lib.h"
#include "ice_vlan_mode.h"
#include "ice.h"
#include "ice_sf_vsi_vlan_ops.h"
void ice_sf_vsi_init_vlan_ops(struct ice_vsi *vsi)
{
struct ice_vsi_vlan_ops *vlan_ops;
if (ice_is_dvm_ena(&vsi->back->hw))
vlan_ops = &vsi->outer_vlan_ops;
else
vlan_ops = &vsi->inner_vlan_ops;
vlan_ops->add_vlan = ice_vsi_add_vlan;
vlan_ops->del_vlan = ice_vsi_del_vlan;
}
Annotation
- Immediate include surface: `ice_vsi_vlan_ops.h`, `ice_vsi_vlan_lib.h`, `ice_vlan_mode.h`, `ice.h`, `ice_sf_vsi_vlan_ops.h`.
- Detected declarations: `function ice_sf_vsi_init_vlan_ops`.
- 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.