<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/Documentation/process/index.rst, branch linux-6.3.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.3.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.3.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2023-03-12T14:56:43Z</updated>
<entry>
<title>Documentation/security-bugs: move from admin-guide/ to process/</title>
<updated>2023-03-12T14:56:43Z</updated>
<author>
<name>Vegard Nossum</name>
</author>
<published>2023-03-05T22:00:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=44ac5abac86b20856e6d9e5e5e40dcc2623fe330'/>
<id>urn:sha1:44ac5abac86b20856e6d9e5e5e40dcc2623fe330</id>
<content type='text'>
Jiri Kosina, Jonathan Corbet, and Willy Tarreau all expressed a desire
to move this document under process/.

Create a new section for security issues in the index and group it with
embargoed-hardware-issues.

I'm doing this at the start of the series to make all the subsequent
changes show up in 'git blame'.

Existing references were updated using:

  git grep -l security-bugs ':!Documentation/translations/' | xargs sed -i 's|admin-guide/security-bugs|process/security-bugs|g'
  git grep -l security-bugs Documentation/translations/ | xargs sed -i 's|Documentation/admin-guide/security-bugs|Documentation/process/security-bugs|g'
  git grep -l security-bugs Documentation/translations/ | xargs sed -i '/Original:/s|\.\./admin-guide/security-bugs|\.\./process/security-bugs|g'

Notably, the page is not moved in the translations (due to my lack of
knowledge of these languages), but the translations have been updated
to point to the new location of the original document where these
references exist.

Link: https://lore.kernel.org/all/nycvar.YFH.7.76.2206062326230.10851@cbobk.fhfr.pm/
Suggested-by: Jiri Kosina &lt;jikos@kernel.org&gt;
Cc: Alex Shi &lt;alexs@kernel.org&gt;
Cc: Yanteng Si &lt;siyanteng@loongson.cn&gt;
Cc: Hu Haowen &lt;src.res@email.cn&gt;
Cc: Federico Vaga &lt;federico.vaga@vaga.pv.it&gt;
Cc: Tsugikazu Shibata &lt;tshibata@ab.jp.nec.com&gt;
Cc: Minchan Kim &lt;minchan@kernel.org&gt;
Cc: Jeimi Lee &lt;jamee.lee@samsung.com&gt;
Cc: Carlos Bilbao &lt;carlos.bilbao@amd.com&gt;
Cc: Akira Yokosawa &lt;akiyks@gmail.com&gt;
Signed-off-by: Vegard Nossum &lt;vegard.nossum@oracle.com&gt;
Acked-by: Carlos Bilbao &lt;carlos.bilbao@amd.com&gt;
Reviewed-by: Yanteng Si &lt;siyanteng@loongson.cn&gt;
Reviewed-by: Akira Yokosawa &lt;akiyks@gmail.com&gt;
Acked-by: Federico Vaga &lt;federico.vaga@vaga.pv.it&gt;
Reviewed-by: Bagas Sanjaya &lt;bagasdotme@gmail.com&gt;
Link: https://lore.kernel.org/r/20230305220010.20895-2-vegard.nossum@oracle.com
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>docs: promote the title of process/index.rst</title>
<updated>2022-09-29T18:55:05Z</updated>
<author>
<name>Jonathan Corbet</name>
</author>
<published>2022-09-27T16:05:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9d0f5cd167444dcffcd46fe19a2cf86f30371f5c'/>
<id>urn:sha1:9d0f5cd167444dcffcd46fe19a2cf86f30371f5c</id>
<content type='text'>
...otherwise Sphinx won't cooperate when trying to list it explicitly in
the top-level index.rst file

Reviewed-by: David Vernet &lt;void@manifault.com&gt;
Acked-by: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
Acked-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;
Link: https://lore.kernel.org/r/20220927160559.97154-2-corbet@lwn.net
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docs: process: remove outdated submitting-drivers.rst</title>
<updated>2022-07-14T21:03:57Z</updated>
<author>
<name>Lukas Bulwahn</name>
</author>
<published>2022-07-04T12:25:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9db370de278087321840ea904d877803a78fba71'/>
<id>urn:sha1:9db370de278087321840ea904d877803a78fba71</id>
<content type='text'>
Commit 31b24bee3357 ("docs: add a warning to submitting-drivers.rst")
in October 2016 already warns "This (...) should maybe just be deleted,
but I'm not quite ready to do that yet".

Maybe, six years ago, we were not ready but let us remove old content
for the better now and structure and maintain less content in the kernel
documentation with a better result.

Drop this already outdated document and adjust all textual references.

Here is an argument why deleting the content will not remove any useful
information to the existing kernel documentation, individually broken down
for each section.

Section "Allocating Device Numbers" refers to https://www.lanana.org/, and
then refers to Documentation/admin-guide/devices.rst.

However, the devices.rst clearly states:

  "The version of this document at lanana.org is no longer maintained."

Everything needed for submitting drivers is already stated in devices.rst
and the reference to https://www.lanana.org/ is outdated, and should be
just deleted.

Section "Who To Submit Drivers To" is all about Linux 2.0 - 2.6, before
the new release version scheme; the mentioned developers are still around,
but actually not the first developers to contact anymore.

Section "What Criteria Determine Acceptance" has a few bullet points:

Licensing and Copyright is well-covered in process/kernel-license.rst.

Interfaces, Code, Portability, Clarity state some obvious things about
ensuring kernel code quality.

Control suggests to add a MAINTAINERS entry, which is already mentioned in
6.Followthrough.rst: "... added yourself to the MAINTAINERS file..."

PM support states a bit about implementing and testing power management of
a driver, it remains an open question where to place that in the process
documents. Driver developers interested in power management will find the
corresponding part on power management in the kernel documentation anyway.

In section "What Criteria Do Not Determine Acceptance", the points Vendor
and Author states something basic consequence of the kernel being an
open-source community software development. Probably no need to mention it
nowadays.

Section "Resources" lists resources that are also mentioned elsewhere more
central.

  - Linux kernel tree and mailing list is mentioned in many places.
  - https://lwn.net/Kernel/LDD3/ is mentioned in
    Documentation/process/kernel-docs.rst.

  - https://lwn.net/ is mentioned in:
    - Documentation/process/8.Conclusion.rst
    - Documentation/process/kernel-docs.rst

  - https://kernelnewbies.org/ is mentioned in:
      - Documentation/process/8.Conclusion.rst
      - Documentation/process/kernel-docs.rst

  - http://www.linux-usb.org/ is mentioned in
    Documentation/driver-api/usb/usb.rst

  - https://landley.net/kdocs/ols/2002/ols2002-pages-545-555.pdf
    is mentioned in Documentation/process/kernel-docs.rst

  - https://kernelnewbies.org/KernelJanitors is mentioned in
    Documentation/process/howto.rst

  - https://git-scm.com/ is mentioned in
    - Documentation/process/2.Process.rst
    - Documentation/process/7.AdvancedTopics.rst
    - Documentation/process/howto.rst

Signed-off-by: Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;
Link: https://lore.kernel.org/r/20220704122537.3407-7-lukas.bulwahn@gmail.com
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>Documentation/process: Add Researcher Guidelines</title>
<updated>2022-03-09T23:19:23Z</updated>
<author>
<name>Kees Cook</name>
</author>
<published>2022-03-04T18:14:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f09f6f9b69821c9efcf16e6b5b466ce9e263ca51'/>
<id>urn:sha1:f09f6f9b69821c9efcf16e6b5b466ce9e263ca51</id>
<content type='text'>
As a follow-up to the UMN incident[1], the TAB took the responsibility
to document Researcher Guidelines so there would be a common place to
point for describing our expectations as a developer community.

Document best practices researchers should follow to participate
successfully with the Linux developer community.

[1] https://lore.kernel.org/lkml/202105051005.49BFABCE@keescook/

Co-developed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Co-developed-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
Co-developed-by: Stefano Zacchiroli &lt;zack@upsilon.cc&gt;
Signed-off-by: Stefano Zacchiroli &lt;zack@upsilon.cc&gt;
Co-developed-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
Acked-by: Steve Rostedt &lt;rostedt@goodmis.org&gt;
Acked-by: Laura Abbott &lt;labbott@kernel.org&gt;
Reviewed-by: Julia Lawall &lt;julia.lawall@inria.fr&gt;
Reviewed-by: Wenwen Wang &lt;wenwen@cs.uga.edu&gt;
Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Link: https://lore.kernel.org/r/20220304181418.1692016-1-keescook@chromium.org
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docs: add two documents about regression handling</title>
<updated>2022-02-24T19:57:25Z</updated>
<author>
<name>Thorsten Leemhuis</name>
</author>
<published>2022-02-16T06:51:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1ecf393fc5a5962ebbe8d011dede6cab880f349b'/>
<id>urn:sha1:1ecf393fc5a5962ebbe8d011dede6cab880f349b</id>
<content type='text'>
Create two documents explaining various aspects around regression
handling and tracking; one is aimed at users, the other targets
developers.

The texts among others describes the first rule of Linux kernel
development and what it means in practice. They also explain what a
regression actually is and how to report one properly.

Both texts additionally provide a brief introduction to the bot the
kernel's regression tracker uses to facilitate the work, but mention the
use is optional.

To sum things up, provide a few quotes from Linus in the document for
developers to show how serious we take regressions.

Signed-off-by: Thorsten Leemhuis &lt;linux@leemhuis.info&gt;
Link: https://lore.kernel.org/r/34e56d3588f22d7e0b4d635ef9c9c3b33ca4ac04.1644994117.git.linux@leemhuis.info
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>Documentation/process: Add maintainer handbooks section</title>
<updated>2021-09-14T20:46:49Z</updated>
<author>
<name>Thomas Gleixner</name>
</author>
<published>2021-09-13T15:39:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=604370e106cca376f7fff2418a9c858b41bb5fd6'/>
<id>urn:sha1:604370e106cca376f7fff2418a9c858b41bb5fd6</id>
<content type='text'>
General rules for patch submission, coding style and related details are
available, but most subsystems have their subsystem-specific extra rules
which differ or go beyond the common rules.

Mark suggested to add a subsystem/maintainer handbook section, where
subsystem maintainers can explain their specific quirks.

Add the section and link to it from the submitting-patches document.

  [ bp: Add a SPDX identifier. ]

Suggested-by: Mark Brown &lt;broonie@kernel.org&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;
Link: https://lkml.kernel.org/r/20181107171149.074948887@linutronix.de
Link: https://lore.kernel.org/r/20210913153942.15251-2-bp@alien8.de
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docs: process/index.rst: Fix reference to nonexistent document</title>
<updated>2020-07-23T20:26:12Z</updated>
<author>
<name>Daniel W. S. Almeida</name>
</author>
<published>2020-07-18T16:50:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b6667585c28d46017030198403c18d803e0c9e90'/>
<id>urn:sha1:b6667585c28d46017030198403c18d803e0c9e90</id>
<content type='text'>
Fix the following warning:

WARNING: toctree contains reference to nonexistent document
'process/unaligned-memory-access'

The path to the document was wrong.

Signed-off-by: Daniel W. S. Almeida &lt;dwlsalmeida@gmail.com&gt;
Link: https://lore.kernel.org/r/20200718165107.625847-5-dwlsalmeida@gmail.com
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docs: sysctl/kernel: document unaligned controls</title>
<updated>2020-05-26T00:59:59Z</updated>
<author>
<name>Stephen Kitt</name>
</author>
<published>2020-05-15T21:24:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=997c798e1444ad02e8af8b18c869fff5c61867da'/>
<id>urn:sha1:997c798e1444ad02e8af8b18c869fff5c61867da</id>
<content type='text'>
This documents ignore-unaligned-usertrap, unaligned-dump-stack, and
unaligned-trap, based on arch/arc/kernel/unaligned.c,
arch/ia64/kernel/unaligned.c, and arch/parisc/kernel/unaligned.c.

While we're at it, integrate unaligned-memory-access.txt into the docs
tree.

Signed-off-by: Stephen Kitt &lt;steve@sk2.org&gt;
Link: https://lore.kernel.org/r/20200515212443.5012-1-steve@sk2.org
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>Documentation: riscv: add patch acceptance guidelines</title>
<updated>2020-01-05T05:49:01Z</updated>
<author>
<name>Paul Walmsley</name>
</author>
<published>2019-11-23T02:33:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0e194d9da198936fe4fb4c1e031de0f7791c09b8'/>
<id>urn:sha1:0e194d9da198936fe4fb4c1e031de0f7791c09b8</id>
<content type='text'>
Formalize, in kernel documentation, the patch acceptance policy for
arch/riscv.  In summary, it states that as maintainers, we plan to
only accept patches for new modules or extensions that have been
frozen or ratified by the RISC-V Foundation.

We've been following these guidelines for the past few months.  In the
meantime, we've received quite a bit of feedback that it would be
helpful to have these guidelines formally documented.

Based on a suggestion from Matthew Wilcox, we also add a link to this
file to Documentation/process/index.rst, to make this document easier
to find.  The format of this document has also been changed to align
to the format outlined in the maintainer entry profiles, in accordance
with comments from Jon Corbet and Dan Williams.

Signed-off-by: Paul Walmsley &lt;paul.walmsley@sifive.com&gt;
Reviewed-by: Palmer Dabbelt &lt;palmerdabbelt@google.com&gt;
Cc: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;
Cc: Albert Ou &lt;aou@eecs.berkeley.edu&gt;
Cc: Krste Asanovic &lt;krste@berkeley.edu&gt;
Cc: Andrew Waterman &lt;waterman@eecs.berkeley.edu&gt;
Cc: Matthew Wilcox &lt;willy@infradead.org&gt;
Cc: Dan Williams &lt;dan.j.williams@intel.com&gt;
Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;</content>
</entry>
<entry>
<title>docs: move botching-up-ioctls.rst to the process guide</title>
<updated>2019-10-10T17:21:48Z</updated>
<author>
<name>Jonathan Corbet</name>
</author>
<published>2019-10-03T18:58:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5ecd0a06e6bb992c903f5d8a588b78852b9e80a5'/>
<id>urn:sha1:5ecd0a06e6bb992c903f5d8a588b78852b9e80a5</id>
<content type='text'>
This is overall information for kernel developers, and not part of the
user-space API.

Cc: Daniel Vetter &lt;daniel@ffwll.ch&gt;
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
</feed>
