tools/net/sunrpc/xdrgen/templates/C/program/encoder/result.j2

File Facts

System

Linux kernel

Corpus path

tools/net/sunrpc/xdrgen/templates/C/program/encoder/result.j2

Extension

.j2

Size

693 bytes

Lines

28

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: tools

Status

atlas-only

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

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

{# SPDX-License-Identifier: GPL-2.0 #}

/**
 * {{ program }}_svc_encode_{{ result }} - Encode a {{ result }} result
 * @rqstp: RPC transaction context
 * @xdr: target XDR data stream
 *
 * Return values:
 *   %true: procedure results encoded successfully
 *   %false: encode failed
 */
bool {{ program }}_svc_encode_{{ result }}(struct svc_rqst *rqstp, struct xdr_stream *xdr)
{
{% if result == 'void' %}
	return xdrgen_encode_void(xdr);
{% else %}
{% if result in structs %}
	struct {{ result }} *resp = rqstp->rq_resp;

	return xdrgen_encode_{{ result }}(xdr, resp);
{% else %}
	{{ result }} *resp = rqstp->rq_resp;

	return xdrgen_encode_{{ result }}(xdr, *resp);
{% endif %}
{% endif %}
}

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: atlas-only.

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.