From e86b1c48d591d50ca5befb24f9dce013e092b044 Mon Sep 17 00:00:00 2001 From: Enrico Bravi <49145850+cinghioGithub@users.noreply.github.com> Date: Fri, 26 Jul 2024 13:56:56 +0200 Subject: [PATCH 1/2] docs: contribute: update Linux kernel contribution guideline Linux kernel contribution does not happen on Github, but on mailing list. Update this information in the Linux kernel contribution guideline. Signed-off-by: Enrico Bravi --- .../asciidoc/computers/linux_kernel/contribute.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/documentation/asciidoc/computers/linux_kernel/contribute.adoc b/documentation/asciidoc/computers/linux_kernel/contribute.adoc index 07a633587..6f430fe18 100644 --- a/documentation/asciidoc/computers/linux_kernel/contribute.adoc +++ b/documentation/asciidoc/computers/linux_kernel/contribute.adoc @@ -18,6 +18,7 @@ Then, submit a pull request containing your changes to the https://github.com/ra === Contribute to the Linux kernel -First, fork the https://github.com/torvalds/linux[Linux kernel repository] and clone it to your development device. You can then make your changes, test them, and commit them into your fork. +First, clone the https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git[Linux kernel tree] to your development device. You can then make your changes, test them, and commit them into your fork. -Then, submit a pull request containing your changes to the https://github.com/torvalds/linux[Linux kernel repository]. Linux kernel contributors will review your contribution and suggest improvements. Once approved, they'll merge in your changes. Eventually, they'll make their way into a long-term release of the Linux kernel. Once we've tested that long-term release for compatibility with the Raspberry Pi kernel, your changes will make their way into a stable release of the Raspberry Pi kernel. +Once your change is ready you can submit it to the Linux kernel community. Linux kernel development happens on mailing lists, rather than on GitHub, so that your change can become part of Linux, please email it to the community as a patch. Please follow the https://www.kernel.org/doc/html/latest/process/submitting-patches.html[Submitting patches: the essential guide to getting your code into the kernel] in the Linux kernel documentation. +Linux kernel contributors will review your contribution and suggest improvements. Once approved, they'll merge in your changes. Eventually, they'll make their way into a long-term release of the Linux kernel. Once we've tested that long-term release for compatibility with the Raspberry Pi kernel, your changes will make their way into a stable release of the Raspberry Pi kernel. From 8e48cc157df1ae6bc09a85af23c239ef2a31b8ec Mon Sep 17 00:00:00 2001 From: Enrico Bravi <49145850+cinghioGithub@users.noreply.github.com> Date: Mon, 29 Jul 2024 15:23:03 +0200 Subject: [PATCH 2/2] docs: contribute: addressed PR review comments - Fixed style problems - Add Linux kernel coding style reference Signed-off-by: Enrico Bravi --- documentation/asciidoc/computers/linux_kernel/contribute.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/asciidoc/computers/linux_kernel/contribute.adoc b/documentation/asciidoc/computers/linux_kernel/contribute.adoc index 6f430fe18..74d03d865 100644 --- a/documentation/asciidoc/computers/linux_kernel/contribute.adoc +++ b/documentation/asciidoc/computers/linux_kernel/contribute.adoc @@ -18,7 +18,7 @@ Then, submit a pull request containing your changes to the https://github.com/ra === Contribute to the Linux kernel -First, clone the https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git[Linux kernel tree] to your development device. You can then make your changes, test them, and commit them into your fork. +First, clone the https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git[Linux kernel tree] to your development device. You can then make your changes, test them, and commit them into your local tree. -Once your change is ready you can submit it to the Linux kernel community. Linux kernel development happens on mailing lists, rather than on GitHub, so that your change can become part of Linux, please email it to the community as a patch. Please follow the https://www.kernel.org/doc/html/latest/process/submitting-patches.html[Submitting patches: the essential guide to getting your code into the kernel] in the Linux kernel documentation. +Once your change is ready you can submit it to the Linux kernel community. Linux kernel development happens on mailing lists, rather than on GitHub. In order for your change to become part of Linux, please email it to the community as a patch. Please follow https://www.kernel.org/doc/html/latest/process/submitting-patches.html[Submitting patches: the essential guide to getting your code into the kernel] and https://www.kernel.org/doc/html/latest/process/coding-style.html[Linux kernel coding style] in the Linux kernel documentation. Linux kernel contributors will review your contribution and suggest improvements. Once approved, they'll merge in your changes. Eventually, they'll make their way into a long-term release of the Linux kernel. Once we've tested that long-term release for compatibility with the Raspberry Pi kernel, your changes will make their way into a stable release of the Raspberry Pi kernel.