Submitting patches

Community, L. K. (2024). Submitting patches: the essential guide to getting your code into the kernel (Documentation/process/submitting-patches.rst).

Type

Software

Intellectual base

Primary research

Year

2024

Link

no authoritative link yet

Cited by

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Domain-specific

• Collaborative Maintenance
  • Contributors submit patches by email to the subsystem mailing lists named in the repository's MAINTAINERS file

    This sourceStates that kernel patches are submitted by e-mail and that submitters must copy the appropriate subsystem maintainer(s) and list(s), looked up in the MAINTAINERS file.

    SupportedVerified against the source

    Read by an automated reader; not a human review. How support was checked

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Read against the text for 1 of 1 citation: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:a84a5f1862e4 · see in the full table