diff options
Diffstat (limited to 'Documentation/process')
| -rw-r--r-- | Documentation/process/coding-assistants.rst | 12 | ||||
| -rw-r--r-- | Documentation/process/generated-content.rst | 7 | ||||
| -rw-r--r-- | Documentation/process/submitting-patches.rst | 14 |
3 files changed, 19 insertions, 14 deletions
diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst index e71df7d28467..051f0d819f68 100644 --- a/Documentation/process/coding-assistants.rst +++ b/Documentation/process/coding-assistants.rst @@ -15,6 +15,10 @@ kernel development process: * Documentation/process/coding-style.rst * Documentation/process/submitting-patches.rst +For guidelines on content generated by AI coding assistants see: + +* Documentation/process/generated-content.rst + Licensing and Legal Requirements ================================ @@ -43,12 +47,8 @@ When AI tools contribute to kernel development, proper attribution helps track the evolving role of AI in the development process. Contributions should include an Assisted-by tag in the following format:: - Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2] - -Where: + Assisted-by: LLM [TOOL1] [TOOL2] -* ``AGENT_NAME`` is the name of the AI tool or framework -* ``MODEL_VERSION`` is the specific model version used * ``[TOOL1] [TOOL2]`` are optional specialized analysis tools used (e.g., coccinelle, sparse, smatch, clang-tidy) @@ -56,7 +56,7 @@ Basic development tools (git, gcc, make, editors) should not be listed. Example:: - Assisted-by: Claude:claude-3-opus coccinelle sparse + Assisted-by: LLM coccinelle sparse Procedure for finding and fixing bugs ===================================== diff --git a/Documentation/process/generated-content.rst b/Documentation/process/generated-content.rst index 08621e50a462..aad2caad9f8b 100644 --- a/Documentation/process/generated-content.rst +++ b/Documentation/process/generated-content.rst @@ -107,3 +107,10 @@ the resulting changes. If you do so anyway, maintainers are entitled to reject your series without detailed review. + +References +========== + +For specific guidelines on AI coding assistants, see: + +* Documentation/process/coding-assistants.rst diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index cc6a1f73d7f2..7ae79452e1b4 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -404,12 +404,11 @@ patches that are being emailed around. The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch. The rules are pretty simple: if you -can certify the below: +can certify the below:: -Developer's Certificate of Origin 1.1 -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + Developer's Certificate of Origin 1.1 -By making a contribution to this project, I certify that: + By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license @@ -554,12 +553,11 @@ some testing has been performed, provides a means to locate testers for future patches, and ensures credit for the testers. Reviewed-by:, instead, indicates that the patch has been reviewed and found -acceptable according to the Reviewer's Statement: +acceptable according to the Reviewer's Statement:: -Reviewer's statement of oversight -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + Reviewer's statement of oversight -By offering my Reviewed-by: tag, I state that: + By offering my Reviewed-by: tag, I state that: (a) I have carried out a technical review of this patch to evaluate its appropriateness and readiness for inclusion into |