tools/net/ynl/tests/devlink.c

File Facts

System

Linux kernel

Corpus path

tools/net/ynl/tests/devlink.c

Extension

.c

Size

2397 bytes

Lines

102

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• stdio.h
• string.h
• ynl.h
• kselftest_harness.h
• devlink-user.h

Detected Declarations

• function ynl_dump_foreach
• function ynl_dump_foreach
• function ASSERT_NE

Annotated Snippet

ASSERT_NE(NULL, info_rsp) {
			devlink_get_list_free(devs);
			TH_LOG("info_get failed: %s", self->ys->err.msg);
		}

		EXPECT_TRUE((bool)info_rsp->_len.info_driver_name);
		if (info_rsp->_len.info_driver_name)
			ksft_print_msg("  driver: %s\n",
				       info_rsp->info_driver_name);
		if (info_rsp->_count.info_version_running)
			ksft_print_msg("  running fw:\n");
		for (i = 0; i < info_rsp->_count.info_version_running; i++)
			ksft_print_msg("    %s: %s\n",
				       info_rsp->info_version_running[i].info_version_name,
				       info_rsp->info_version_running[i].info_version_value);
		devlink_info_get_rsp_free(info_rsp);
	}
	devlink_get_list_free(devs);
}

TEST_HARNESS_MAIN

Annotation

• Immediate include surface: `stdio.h`, `string.h`, `ynl.h`, `kselftest_harness.h`, `devlink-user.h`.
• Detected declarations: `function ynl_dump_foreach`, `function ynl_dump_foreach`, `function ASSERT_NE`.
• Atlas domain: Support Tooling And Documentation / tools.
• 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.