Skip to contentSkip to conversation

docs: remove submitting-drivers.rst

PATCH In review Lukas Bulwahn 4 participants 17 messages Jul 4, 2022 – Jul 14, 2022

Subsystems (9)
lore
Share & tools
lore
#0 lore raw

cover docs: remove submitting-drivers.rst

Dear Jonathan, dear Federico, dear Alex, dear Yanteng, dear Hu,

Here is an attempt to delete submitting-drivers with some improvements and clean-up in other documentation places to convince ourselves that nothing valuable is lost when deleting this checklist.

Patch 1, 2 and 3 is just basic clean-up before adding a new reference (see Patch 4). Patch 4 adds the one reference from submitting-drivers, not already mentioned elsewhere in the repository. Patch 5 updates a confusing statement in devices.rst from earlier .txt/.tex distinction times to the new state now with Sphinx & .rst.

Patch 6 finally deletes the outdated document, with a cross-check what is covered elsewhere and few open questions (see below).

Patch 7 and 8 have been reworked with the native-speaking doc maintainers; they cause no new warnings and are ready to pick,

Patch 9 to 11 are weak attempts to adjust the translation, but they need to be taken further by others due to my lack of knowledge on the other languages. They would currently also cause new warnings in the doc-build right now. They should not be picked if there is no one to continue to adjust the text and fix the warnings on broken references.

I hope that patches 1 to 8 can be picked into doc-next, and then we see how to fix up the translations as well.

Further open considerations:

- Should we add some subsection/paragraph on Testing to "A guide on kernel development process", which then further refers to power/drivers-testing.rst for testing the power management of the driver?

(I am bit surprised that code-checking tools are mentioned, but not much more on actual kernel testing is mentioned there.)

- Should we be a bit more explicit on how and when to add a MAINTAINERS entry, besides the short note in 6.Followthrough.rst?

- Translations of submitting-patches.rst and 8.Conclusion.rst in Asian languages include a reference to submitting-drivers, I cannot adjust the text due to my lack of understanding of the surrounding text.

zh_CN/process/8.Conclusion.rst:和 :ref:Documentation/translations/zh_CN/process/submitting-drivers.rst <cn_submittingdrivers> zh_CN/process/submitting-patches.rst::ref:Documentation/process/submitting-drivers.rst <submittingdrivers> zh_TW/process/8.Conclusion.rst:和 :ref:Documentation/translations/zh_TW/process/submitting-drivers.rst <tw_submittingdrivers> zh_TW/process/submitting-patches.rst::ref:Documentation/process/submitting-drivers.rst <submittingdrivers>

This currently lead to some new warnings in this patch series. I hope some native speakers of those languages can help out here. The other references were adjusted on a best guess of the text, which should be confirmed by native-speaking reviewers.

Generally, I hope we are now all well-convinced to delete submitting-drivers.

Anything else needed to be convinced? I put already some thought into it, and I am willing to add more content in other documents to properly get rid of this outdated one here, or just starting writing a good new checklist for driver submission that reflect what the majority of maintainers want to see submitters do.

Link to RFC patch series:
https://lore.kernel.org/linux-doc/[email protected]/

rfc -> v1: improved Italian and Japanese translation

Best regards,

Lukas

Lukas Bulwahn (11):
docs: kernel-docs: order reference from newest to oldest
docs: kernel-docs: shorten the lengthy doc title
docs: kernel-docs: reflect that it is community-maintained
docs: kernel-docs: add a reference mentioned in submitting-drivers.rst
docs: admin: devices: drop confusing outdated statement on Latex
docs: process: remove outdated submitting-drivers.rst
docs: it_IT: align to submitting-drivers removal
docs: ja_JP: howto: remove reference to removed submitting-drivers
docs: ko_KR: howto: remove reference to removed submitting-drivers
docs: zh_CN: align to submitting-drivers removal
docs: zh_TW: align to submitting-drivers removal

 Documentation/admin-guide/devices.rst         |   7 +-
 Documentation/hwmon/submitting-patches.rst    |   1 -
 Documentation/kernel-hacking/hacking.rst      |   3 +-
 Documentation/process/5.Posting.rst           |   3 +-
 Documentation/process/8.Conclusion.rst        |  16 +-
 Documentation/process/howto.rst               |   4 +-
 Documentation/process/index.rst               |   1 -
 Documentation/process/kernel-docs.rst         |  62 +++---
 Documentation/process/submitting-drivers.rst  | 194 ------------------
 Documentation/process/submitting-patches.rst  |   5 +-
 .../it_IT/kernel-hacking/hacking.rst          |   3 +-
 .../translations/it_IT/process/5.Posting.rst  |   5 +-
 .../it_IT/process/8.Conclusion.rst            |   5 +-
 .../translations/it_IT/process/howto.rst      |   3 +-
 .../translations/it_IT/process/index.rst      |   1 -
 .../it_IT/process/submitting-drivers.rst      |  16 --
 .../it_IT/process/submitting-patches.rst      |   6 +-
 Documentation/translations/ja_JP/howto.rst    |   4 +-
 Documentation/translations/ko_KR/howto.rst    |   2 +-
 .../zh_CN/kernel-hacking/hacking.rst          |   3 +-
 .../translations/zh_CN/process/5.Posting.rst  |   3 +-
 .../translations/zh_CN/process/howto.rst      |   1 -
 .../translations/zh_CN/process/index.rst      |   1 -
 .../zh_CN/process/submitting-drivers.rst      | 160 ---------------
 .../translations/zh_TW/process/5.Posting.rst  |   3 +-
 .../translations/zh_TW/process/howto.rst      |   1 -
 .../translations/zh_TW/process/index.rst      |   1 -
 .../zh_TW/process/submitting-drivers.rst      | 164 ---------------
 28 files changed, 66 insertions(+), 612 deletions(-)
 delete mode 100644 Documentation/process/submitting-drivers.rst
 delete mode 100644 Documentation/translations/it_IT/process/submitting-drivers.rst
 delete mode 100644 Documentation/translations/zh_CN/process/submitting-drivers.rst
 delete mode 100644 Documentation/translations/zh_TW/process/submitting-drivers.rst
Signature · 1 line
2.17.1
#1 lore raw

PATCH 1/11 docs: kernel-docs: order reference from newest to oldest

The documents on each section of this document are ordered by its published date, from the newest to the oldest.

In the kernel-docs.rst, the references on each section of this document are intended to be ordered by its published date, from the newest to the oldest. The Linux Kernel Module Programming Guide was published in 2021; so, it is placed at the top as the most recent publication after the rolling-version "Linux Kernel Mailing List Glossary" reference.

Fixes 630c8fa02f9a ("Documentation: Update details of The Linux Kernel Module Programming Guide")
---
 Documentation/process/kernel-docs.rst | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)
Documentation/process/kernel-docs.rst +12 -12
index da9527502ef0..b4d98f6f797a 100644
@@ -83,6 +83,18 @@ On-line docs
         Finally this trace-log is used as base for more a exact conceptual
         exploration and description of the Linux TCP/IP implementation.*
 
+    * Title: **The Linux Kernel Module Programming Guide**
+
+      :Author: Peter Jay Salzman, Michael Burian, Ori Pomerantz, Bob Mottram,
+        Jim Huang.
+      :URL: https://sysprog21.github.io/lkmpg/
+      :Date: 2021
+      :Keywords: modules, GPL book, /proc, ioctls, system calls,
+        interrupt handlers .
+      :Description: A very nice GPL book on the topic of modules
+        programming. Lots of examples. Currently the new version is being
+        actively maintained at https://github.com/sysprog21/lkmpg.
+
     * Title: **On submitting kernel Patches**
 
       :Author: Andi Kleen
@@ -126,18 +138,6 @@ On-line docs
         describes how to write user-mode utilities for communicating with
         Card Services.
 
-    * Title: **The Linux Kernel Module Programming Guide**
-
-      :Author: Peter Jay Salzman, Michael Burian, Ori Pomerantz, Bob Mottram,
-        Jim Huang.
-      :URL: https://sysprog21.github.io/lkmpg/
-      :Date: 2021
-      :Keywords: modules, GPL book, /proc, ioctls, system calls,
-        interrupt handlers .
-      :Description: A very nice GPL book on the topic of modules
-        programming. Lots of examples. Currently the new version is being
-        actively maintained at https://github.com/sysprog21/lkmpg.
-
     * Title: **Global spinlock list and usage**
 
       :Author: Rick Lindsley.
Signature · 1 line
2.17.1
#2 lore raw

PATCH 2/11 docs: kernel-docs: shorten the lengthy doc title

In reply to Lukas Bulwahn

The original title comes from copying the content from a web page that covered various mixed computer-science material. Within the kernel documentation and its current structure, the title can be shortened.

Other titles considered, but not selected were:
- Index of More Kernel Documentation
- Further Kernel Documentation
- References to Further Kernel Documentation

Shorten the title.

---
 Documentation/process/kernel-docs.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/process/kernel-docs.rst +2 -2
index b4d98f6f797a..5d6fa71895cc 100644
@@ -1,7 +1,7 @@
 .. _kernel_docs:
 
-Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel
-=============================================================================================
+Index of Further Kernel Documentation
+=====================================
 
           Juan-Mariano de Goyeneche <[email protected]>
 
Signature · 1 line
2.17.1
#3 lore raw

PATCH 3/11 docs: kernel-docs: reflect that it is community-maintained

In reply to Lukas Bulwahn

Remove and rephrase statements that only make sense if a single author exclusively would maintain this document, but we would really want to consider this being a page maintained by the kernel community, as it is placed in the kernel repository, and let us hope that more contributors suggest some more documents.

Further, do some minor word-smithing.

---
 Documentation/process/kernel-docs.rst | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)
Documentation/process/kernel-docs.rst +9 -13
index 5d6fa71895cc..b2523267ffc7 100644
@@ -3,7 +3,8 @@
 Index of Further Kernel Documentation
 =====================================
 
-          Juan-Mariano de Goyeneche <[email protected]>
+Initial Author: Juan-Mariano de Goyeneche (<[email protected]>;
+email address is defunct now.)
 
 The need for a document like this one became apparent in the
 linux-kernel mailing list as the same questions, asking for pointers
@@ -16,21 +17,16 @@ philosophy and design decisions behind this code.
 
 Unfortunately, not many documents are available for beginners to
 start. And, even if they exist, there was no "well-known" place which
-kept track of them. These lines try to cover this lack. All documents
-available on line known by the author are listed, while some reference
-books are also mentioned.
+kept track of them. These lines try to cover this lack.
 
 PLEASE, if you know any paper not listed here or write a new document,
-send me an e-mail, and I'll include a reference to it here. Any
-corrections, ideas or comments are also welcomed.
+include a reference to it here, following the kernel's patch submission
+process. Any corrections, ideas or comments are also welcome.
 
-The papers that follow are listed in no particular order. All are
-cataloged with the following fields: the document's "Title", the
-"Author"/s, the "URL" where they can be found, some "Keywords" helpful
-when searching for specific topics, and a brief "Description" of the
-Document.
-
-Enjoy!
+All documents are cataloged with the following fields: the document's
+"Title", the "Author"/s, the "URL" where they can be found, some
+"Keywords" helpful when searching for specific topics, and a brief
+"Description" of the Document.
 
 .. note::
 
Signature · 1 line
2.17.1
#4 lore raw

PATCH 4/11 docs: kernel-docs: add a reference mentioned in submitting-drivers.rst

In reply to Lukas Bulwahn

One section in submitting-drivers.rst was just a collection of references to other external documentation. All except the one added in this commit is already mentioned in kernel-docs or other places in the kernel documentation.

Add Arjan van de Ven's article on How to NOT write kernel driver to this index of further kernel documentation.

---
 Documentation/process/kernel-docs.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
Documentation/process/kernel-docs.rst +14 -0
index b2523267ffc7..502289d63385 100644
@@ -134,6 +134,20 @@ On-line docs
         describes how to write user-mode utilities for communicating with
         Card Services.
 
+    * Title: **How NOT to write kernel drivers**
+
+      :Author: Arjan van de Ven.
+      :URL: https://landley.net/kdocs/ols/2002/ols2002-pages-545-555.pdf
+      :Date: 2002
+      :Keywords: driver.
+      :Description: Programming bugs and Do-nots in kernel driver development
+      :Abstract: *Quit a few tutorials, articles and books give an introduction
+        on how to write Linux kernel drivers. Unfortunately the things one
+        should NOT do in Linux kernel code is either only a minor appendix
+        or, more commonly, completely absent. This paper tries to briefly touch
+        the areas in which the most common and serious bugs and do-nots are
+        encountered.*
+
     * Title: **Global spinlock list and usage**
 
       :Author: Rick Lindsley.
Signature · 1 line
2.17.1
#5 lore raw

PATCH 5/11 docs: admin: devices: drop confusing outdated statement on Latex

In reply to Lukas Bulwahn

The statement that the Latex version of Linux Device List is unmaintained, must go back to some historic time where there were actually two separate document sources, one in a txt format and another in a tex format (maybe even just on lanana.org).

Nowadays, html and tex are generated from the ReST document file and the statement might be confused, believing the actual generated LaTeX document from the maintained ReST document could be an unmaintained one.

Remove this statement on the LaTeX version and only keep pointing out that the version on lanana.org is no longer maintained.

---
 Documentation/admin-guide/devices.rst | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
Documentation/admin-guide/devices.rst +3 -4
index 035275fedbdd..e3776d77374b 100644
@@ -7,10 +7,9 @@ This list is the Linux Device List, the official registry of allocated
 device numbers and ``/dev`` directory nodes for the Linux operating
 system.
 
-The LaTeX version of this document is no longer maintained, nor is
-the document that used to reside at lanana.org.  This version in the
-mainline Linux kernel is the master document.  Updates shall be sent
-as patches to the kernel maintainers (see the
+The version of this document at lanana.org is no longer maintained.  This
+version in the mainline Linux kernel is the master document.  Updates
+shall be sent as patches to the kernel maintainers (see the
 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` document).
 Specifically explore the sections titled "CHAR and MISC DRIVERS", and
 "BLOCK LAYER" in the MAINTAINERS file to find the right maintainers
Signature · 1 line
2.17.1
#6 lore raw

PATCH 6/11 docs: process: remove outdated submitting-drivers.rst

In reply to Lukas Bulwahn

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

---
 Documentation/hwmon/submitting-patches.rst   |   1 -
 Documentation/kernel-hacking/hacking.rst     |   3 +-
 Documentation/process/5.Posting.rst          |   3 +-
 Documentation/process/8.Conclusion.rst       |  16 +-
 Documentation/process/howto.rst              |   4 +-
 Documentation/process/index.rst              |   1 -
 Documentation/process/submitting-drivers.rst | 194 -------------------
 Documentation/process/submitting-patches.rst |   5 +-
 8 files changed, 13 insertions(+), 214 deletions(-)
 delete mode 100644 Documentation/process/submitting-drivers.rst
Documentation/hwmon/submitting-patches.rst +0 -1
index 9a218ea996d8..d953ee763c96 100644
@@ -12,7 +12,6 @@ increase the chances of your change being accepted.
 * It should be unnecessary to mention, but please read and follow:
 
     - Documentation/process/submit-checklist.rst
-    - Documentation/process/submitting-drivers.rst
     - Documentation/process/submitting-patches.rst
     - Documentation/process/coding-style.rst
 
Documentation/kernel-hacking/hacking.rst +1 -2
index ebd9d90882ea..9a1f020c8449 100644
@@ -755,8 +755,7 @@ make a neat patch, there's administrative work to be done:
    it implies a more-than-passing commitment to some part of the code.
 
 -  Finally, don't forget to read
-   ``Documentation/process/submitting-patches.rst`` and possibly
-   ``Documentation/process/submitting-drivers.rst``.
+   ``Documentation/process/submitting-patches.rst``
 
 Kernel Cantrips
 ===============
Documentation/process/5.Posting.rst +1 -2
index bd36ecb29409..906235c11c24 100644
@@ -10,8 +10,7 @@ of conventions and procedures which are used in the posting of patches;
 following them will make life much easier for everybody involved.  This
 document will attempt to cover these expectations in reasonable detail;
 more information can also be found in the files
-:ref:`Documentation/process/submitting-patches.rst <submittingpatches>`,
-:ref:`Documentation/process/submitting-drivers.rst  <submittingdrivers>`
+:ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
 and :ref:`Documentation/process/submit-checklist.rst <submitchecklist>`.
 
 
Documentation/process/8.Conclusion.rst +7 -9
index b32a40215858..8c847dffe76b 100644
@@ -5,15 +5,13 @@ For more information
 
 There are numerous sources of information on Linux kernel development and
 related topics.  First among those will always be the Documentation
-directory found in the kernel source distribution.  The top-level :ref:`process/howto.rst <process_howto>`
-file is an important starting point; :ref:`process/submitting-patches.rst <submittingpatches>`
-and :ref:`process/submitting-drivers.rst  <submittingdrivers>`
-are also something which all kernel developers should
-read.  Many internal kernel APIs are documented using the kerneldoc
-mechanism; "make htmldocs" or "make pdfdocs" can be used to generate those
-documents in HTML or PDF format (though the version of TeX shipped by some
-distributions runs into internal limits and fails to process the documents
-properly).
+directory found in the kernel source distribution.  Start with the
+top-level :ref:`process/howto.rst <process_howto>`; also read
+:ref:`process/submitting-patches.rst <submittingpatches>`. Many internal
+kernel APIs are documented using the kerneldoc mechanism; "make htmldocs"
+or "make pdfdocs" can be used to generate those documents in HTML or PDF
+format (though the version of TeX shipped by some distributions runs into
+internal limits and fails to process the documents properly).
 
 Various web sites discuss kernel development at all levels of detail.  Your
 author would like to humbly suggest https://lwn.net/ as a source;
Documentation/process/howto.rst +2 -2
index e4beeca57e5f..cd6997a9d203 100644
@@ -105,8 +105,8 @@ required reading:
     patches if these rules are followed, and many people will only
     review code if it is in the proper style.
 
-  :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` and :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
-    These files describe in explicit detail how to successfully create
+  :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
+    This file describes in explicit detail how to successfully create
     and send a patch, including (but not limited to):
 
        - Email contents
Documentation/process/index.rst +0 -1
index 3587dae4d0ef..2ba2a1582bbe 100644
@@ -40,7 +40,6 @@ Other guides to the community that are of interest to most developers are:
    :maxdepth: 1
 
    changes
-   submitting-drivers
    stable-api-nonsense
    management-style
    stable-kernel-rules
Documentation/process/submitting-drivers.rst deleted +0 -194

194 lines not on this page · raw message

Documentation/process/submitting-patches.rst +2 -3
index a1cb6280fbcf..be49d8f2601b 100644
@@ -12,9 +12,8 @@ This document contains a large number of suggestions in a relatively terse
 format.  For detailed information on how the kernel development process
 works, see Documentation/process/development-process.rst. Also, read
 Documentation/process/submit-checklist.rst
-for a list of items to check before submitting code.  If you are submitting
-a driver, also read Documentation/process/submitting-drivers.rst; for device
-tree binding patches, read
+for a list of items to check before submitting code.
+For device tree binding patches, read
 Documentation/devicetree/bindings/submitting-patches.rst.
 
 This documentation assumes that you're using ``git`` to prepare your patches.
Signature · 1 line
2.17.1
#7 lore raw

PATCH 7/11 docs: it_IT: align to submitting-drivers removal

In reply to Lukas Bulwahn

Adjust the Italian translation to the removal of submitting-drivers in the English kernel documentation, with some assistance from Frederico Vaga.

---
 .../it_IT/kernel-hacking/hacking.rst             |  3 +--
 .../translations/it_IT/process/5.Posting.rst     |  5 ++---
 .../translations/it_IT/process/8.Conclusion.rst  |  5 ++---
 .../translations/it_IT/process/howto.rst         |  3 +--
 .../translations/it_IT/process/index.rst         |  1 -
 .../it_IT/process/submitting-drivers.rst         | 16 ----------------
 .../it_IT/process/submitting-patches.rst         |  6 ++----
 7 files changed, 8 insertions(+), 31 deletions(-)
 delete mode 100644 Documentation/translations/it_IT/process/submitting-drivers.rst
Documentation/translations/it_IT/kernel-hacking/hacking.rst +1 -2
index d5c521327f6a..4bec4669cf48 100644
@@ -795,8 +795,7 @@ anche per avere patch pulite, c'è del lavoro amministrativo da fare:
    di un semplice impegno su una parte del codice.
 
 -  Infine, non dimenticatevi di leggere
-   ``Documentation/process/submitting-patches.rst`` e possibilmente anche
-   ``Documentation/process/submitting-drivers.rst``.
+   ``Documentation/process/submitting-patches.rst``.
 
 Trucchetti del kernel
 =====================
Documentation/translations/it_IT/process/5.Posting.rst +2 -3
index 1476d51eb5e5..a036f38fc82e 100644
@@ -16,9 +16,8 @@ e di procedure per la pubblicazione delle patch; seguirle renderà la vita
 più facile a tutti quanti.  Questo documento cercherà di coprire questi
 argomenti con un ragionevole livello di dettaglio; più informazioni possono
 essere trovare nella cartella 'Documentation', nei file
-:ref:`translations/it_IT/process/submitting-patches.rst <it_submittingpatches>`,
-:ref:`translations/it_IT/process/submitting-drivers.rst <it_submittingdrivers>`, e
-:ref:`translations/it_IT/process/submit-checklist.rst <it_submitchecklist>`.
+:ref:`translations/it_IT/process/submitting-patches.rst <it_submittingpatches>`
+e :ref:`translations/it_IT/process/submit-checklist.rst <it_submitchecklist>`.
 
 
 Quando pubblicarle
Documentation/translations/it_IT/process/8.Conclusion.rst +2 -3
index 039bfc5a4108..32659ff467c0 100644
@@ -13,9 +13,8 @@ e argomenti correlati. Primo tra questi sarà sempre la cartella Documentation
 che si trova nei sorgenti kernel.
 
 Il file :ref:`process/howto.rst <it_process_howto>` è un punto di partenza
-importante; :ref:`process/submitting-patches.rst <it_submittingpatches>` e
-:ref:`process/submitting-drivers.rst <it_submittingdrivers>` sono
-anch'essi qualcosa che tutti gli sviluppatori del kernel dovrebbero leggere.
+importante; :ref:`process/submitting-patches.rst <it_submittingpatches>` è
+anch'esso qualcosa che tutti gli sviluppatori del kernel dovrebbero leggere.
 Molte API interne al kernel sono documentate utilizzando il meccanismo
 kerneldoc; "make htmldocs" o "make pdfdocs" possono essere usati per generare
 quei documenti in HTML o PDF (sebbene le versioni di TeX di alcune
Documentation/translations/it_IT/process/howto.rst +1 -2
index 9554368a2ae2..16ad5622d549 100644
@@ -109,8 +109,7 @@ Di seguito una lista di file che sono presenti nei sorgente del kernel e che
     accetteranno patch solo se queste osserveranno tali regole, e molte
     persone revisioneranno il codice solo se scritto nello stile appropriato.
 
-  :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>` e
-  :ref:`Documentation/translations/it_IT/process/submitting-drivers.rst <it_submittingdrivers>`
+  :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>`
 
     Questo file descrive dettagliatamente come creare ed inviare una patch
     con successo, includendo (ma non solo questo):
Documentation/translations/it_IT/process/index.rst +0 -1
index c4c867132c88..b223b70a4a95 100644
@@ -41,7 +41,6 @@ degli sviluppatori:
    :maxdepth: 1
 
    changes
-   submitting-drivers
    stable-api-nonsense
    management-style
    stable-kernel-rules
Documentation/translations/it_IT/process/submitting-drivers.rst deleted +0 -16
deleted file mode 100644
index dadd77e47613..000000000000
@@ -1,16 +0,0 @@
-.. include:: ../disclaimer-ita.rst
-
-:Original: :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
-:Translator: Federico Vaga <[email protected]>
-
-.. _it_submittingdrivers:
-
-Sottomettere driver per il kernel Linux
-=======================================
-
-.. note::
-
-   Questo documento è vecchio e negli ultimi anni non è stato più aggiornato;
-   dovrebbe essere aggiornato, o forse meglio, rimosso.  La maggior parte di
-   quello che viene detto qui può essere trovato anche negli altri documenti
-   dedicati allo sviluppo.  Per questo motivo il documento non verrà tradotto.
Documentation/translations/it_IT/process/submitting-patches.rst +2 -4
index 4fb5b3aa306d..f117ee0a36e2 100644
@@ -18,10 +18,8 @@ Questo documento contiene un vasto numero di suggerimenti concisi. Per maggiori
 dettagli su come funziona il processo di sviluppo del kernel leggete
 Documentation/translations/it_IT/process/development-process.rst. Leggete anche
 Documentation/translations/it_IT/process/submit-checklist.rst per una lista di
-punti da verificare prima di inviare del codice. Se state inviando un driver,
-allora leggete anche
-Documentation/translations/it_IT/process/submitting-drivers.rst; per delle patch
-relative alle associazioni per Device Tree leggete
+punti da verificare prima di inviare del codice.
+Per delle patch relative alle associazioni per Device Tree leggete
 Documentation/translations/it_IT/process/submitting-patches.rst.
 
 Questa documentazione assume che sappiate usare ``git`` per preparare le patch.
Signature · 1 line
2.17.1
#8 lore raw

PATCH 8/11 docs: ja_JP: howto: remove reference to removed submitting-drivers

In reply to Lukas Bulwahn

The document submitting-drivers.rst was deleted. This removes the corresponding reference in the Japanese translation of the howto, with some assistance from Akira Yokasawa.

---
 Documentation/translations/ja_JP/howto.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/translations/ja_JP/howto.rst +2 -2
index 38fed6fe62fe..649e2ff2a407 100644
@@ -129,8 +129,8 @@ [email protected] に送ることを勧めます。
     ルに従っているものだけを受け付け、多くの人は正しいスタイルのコード
     だけをレビューします。
 
-  :ref:`Documentation/process/submitting-patches.rst <codingstyle>` と :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
-    これらのファイルには、どうやってうまくパッチを作って投稿するかにつ
+  :ref:`Documentation/process/submitting-patches.rst <codingstyle>`
+    このファイルには、どうやってうまくパッチを作って投稿するかにつ
     いて非常に詳しく書かれており、以下を含みます (これだけに限らない
     けれども)
 
Signature · 1 line
2.17.1
reviewer Reviewed-by on v1 8/11
#9 lore raw

Re: [PATCH 08/11] docs: ja_JP: howto: remove reference to removed submitting-drivers

Quoted 6 lines · Lukas Bulwahn

The document submitting-drivers.rst was deleted. This removes the corresponding reference in the Japanese translation of the howto, with some assistance from Akira Yokasawa.

Thanks, Akira

Quoted 21 lines
---
 Documentation/translations/ja_JP/howto.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/translations/ja_JP/howto.rst +2 -2
index 38fed6fe62fe..649e2ff2a407 100644
@@ -129,8 +129,8 @@ [email protected] に送ることを勧めます。
     ルに従っているものだけを受け付け、多くの人は正しいスタイルのコード
     だけをレビューします。
 
-  :ref:`Documentation/process/submitting-patches.rst <codingstyle>` と :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
-    これらのファイルには、どうやってうまくパッチを作って投稿するかにつ
+  :ref:`Documentation/process/submitting-patches.rst <codingstyle>`
+    このファイルには、どうやってうまくパッチを作って投稿するかにつ
     いて非常に詳しく書かれており、以下を含みます (これだけに限らない
     けれども)
 
Signature · 1 line
2.17.1
#10 lore raw

PATCH 9/11 docs: ko_KR: howto: remove reference to removed submitting-drivers

In reply to Lukas Bulwahn

The document submitting-drivers.rst was deleted. This removes the corresponding reference in the Korean translation of the howto.

---
 Documentation/translations/ko_KR/howto.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/translations/ko_KR/howto.rst +1 -1
index e3cdf0c84892..e43970584ca4 100644
@@ -124,7 +124,7 @@ [email protected]의 메인테이너에게 보낼 것을 권장한다.
     메인테이너들은 이 규칙을 따르는 패치들만을 받아들일 것이고 많은 사람들이
     그 패치가 올바른 스타일일 경우만 코드를 검토할 것이다.
 
-  :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` 와 :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
+  :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
     이 파일들은 성공적으로 패치를 만들고 보내는 법을 다음의 내용들로
     굉장히 상세히 설명하고 있다(그러나 다음으로 한정되진 않는다).
 
Signature · 1 line
2.17.1
#11 lore raw

PATCH 10/11 docs: zh_CN: align to submitting-drivers removal

In reply to Lukas Bulwahn

Adjust the Chinese translation to the removal of submitting-drivers in the English kernel documentation.

---
 .../zh_CN/kernel-hacking/hacking.rst          |   3 +-
 .../translations/zh_CN/process/5.Posting.rst  |   3 +-
 .../translations/zh_CN/process/howto.rst      |   1 -
 .../translations/zh_CN/process/index.rst      |   1 -
 .../zh_CN/process/submitting-drivers.rst      | 160 ------------------
 5 files changed, 2 insertions(+), 166 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/process/submitting-drivers.rst
Documentation/translations/zh_CN/kernel-hacking/hacking.rst +1 -2
index f2bc154c5bcc..2c85ddfbfd3a 100644
@@ -633,8 +633,7 @@ C++
    文件(无论如何你的名字都应该在源文件的顶部)。维护人员意味着您希望在对
    子系统进行更改时得到询问,并了解缺陷;这意味着对某部分代码做出更多承诺。
 
--  最后,别忘记去阅读 Documentation/process/submitting-patches.rst ,
-   也许还有 Documentation/process/submitting-drivers.rst 。
+-  最后,别忘记去阅读 Documentation/process/submitting-patches.rst。
 
 Kernel 仙女棒
 ===============
Documentation/translations/zh_CN/process/5.Posting.rst +1 -2
index 4ee7de13f373..6a469e1c7deb 100644
@@ -19,8 +19,7 @@
 内核开发社区已经发展出一套用于发布补丁的约定和过程;遵循这些约定和过程将使
 参与其中的每个人的生活更加轻松。本文档试图描述这些约定的部分细节;更多信息
 也可在以下文档中找到
-:ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`,
-:ref:`Documentation/translations/zh_CN/process/submitting-drivers.rst <cn_submittingdrivers>`
+:ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
 和 :ref:`Documentation/translations/zh_CN/process/submit-checklist.rst <cn_submitchecklist>`。
 
 何时寄送
Documentation/translations/zh_CN/process/howto.rst +0 -1
index 1334cdb32a3c..1455190dc087 100644
@@ -96,7 +96,6 @@ Linux内核代码中包含有大量的文档。这些文档对于学习如何与
     的代码。
 
   :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
-  :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
 
     这两份文档明确描述如何创建和发送补丁,其中包括(但不仅限于):
        - 邮件内容
Documentation/translations/zh_CN/process/index.rst +0 -1
index 39e9c88fbaa6..a683dbea0c83 100644
@@ -40,7 +40,6 @@
 .. toctree::
    :maxdepth: 1
 
-   submitting-drivers
    submit-checklist
    stable-api-nonsense
    stable-kernel-rules
Documentation/translations/zh_CN/process/submitting-drivers.rst deleted +0 -160

160 lines not on this page · raw message

Signature · 1 line
2.17.1
Reviewed-by on v1 10/11
#12 lore raw

Re: [PATCH 10/11] docs: zh_CN: align to submitting-drivers removal

Quoted 5 lines · Lukas Bulwahn

Adjust the Chinese translation to the removal of submitting-drivers in the English kernel documentation.

Quoted 230 lines
---
 .../zh_CN/kernel-hacking/hacking.rst          |   3 +-
 .../translations/zh_CN/process/5.Posting.rst  |   3 +-
 .../translations/zh_CN/process/howto.rst      |   1 -
 .../translations/zh_CN/process/index.rst      |   1 -
 .../zh_CN/process/submitting-drivers.rst      | 160 ------------------
 5 files changed, 2 insertions(+), 166 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/process/submitting-drivers.rst
Documentation/translations/zh_CN/kernel-hacking/hacking.rst +1 -2
index f2bc154c5bcc..2c85ddfbfd3a 100644
@@ -633,8 +633,7 @@ C++
    文件(无论如何你的名字都应该在源文件的顶部)。维护人员意味着您希望在对
    子系统进行更改时得到询问,并了解缺陷;这意味着对某部分代码做出更多承诺。
 
--  最后,别忘记去阅读 Documentation/process/submitting-patches.rst ,
-   也许还有 Documentation/process/submitting-drivers.rst 。
+-  最后,别忘记去阅读 Documentation/process/submitting-patches.rst。
 
 Kernel 仙女棒
 ===============
Documentation/translations/zh_CN/process/5.Posting.rst +1 -2
index 4ee7de13f373..6a469e1c7deb 100644
@@ -19,8 +19,7 @@
 内核开发社区已经发展出一套用于发布补丁的约定和过程;遵循这些约定和过程将使
 参与其中的每个人的生活更加轻松。本文档试图描述这些约定的部分细节;更多信息
 也可在以下文档中找到
-:ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`,
-:ref:`Documentation/translations/zh_CN/process/submitting-drivers.rst <cn_submittingdrivers>`
+:ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
 和 :ref:`Documentation/translations/zh_CN/process/submit-checklist.rst <cn_submitchecklist>`。
 
 何时寄送
Documentation/translations/zh_CN/process/howto.rst +0 -1
index 1334cdb32a3c..1455190dc087 100644
@@ -96,7 +96,6 @@ Linux内核代码中包含有大量的文档。这些文档对于学习如何与
     的代码。
 
   :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
-  :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
 
     这两份文档明确描述如何创建和发送补丁,其中包括(但不仅限于):
        - 邮件内容
Documentation/translations/zh_CN/process/index.rst +0 -1
index 39e9c88fbaa6..a683dbea0c83 100644
@@ -40,7 +40,6 @@
 .. toctree::
    :maxdepth: 1
 
-   submitting-drivers
    submit-checklist
    stable-api-nonsense
    stable-kernel-rules
Documentation/translations/zh_CN/process/submitting-drivers.rst deleted +0 -161
deleted file mode 100644
index 98341e7cd812..000000000000
@@ -1,160 +0,0 @@
-.. _cn_submittingdrivers:
-
-.. include:: ../disclaimer-zh_CN.rst
-
-:Original: :ref:`Documentation/process/submitting-drivers.rst
-           <submittingdrivers>`
-
-如果想评论或更新本文的内容,请直接联系原文档的维护者。如果你使用英文
-交流有困难的话,也可以向中文版维护者求助。如果本翻译更新不及时或者翻
-译存在问题,请联系中文版维护者::
-
-        中文版维护者: 李阳  Li Yang <[email protected]>
-        中文版翻译者: 李阳  Li Yang <[email protected]>
-        中文版校译者: 陈琦 Maggie Chen <[email protected]>
-                       王聪 Wang Cong <[email protected]>
-                       张巍 Zhang Wei <[email protected]>
-
-如何向 Linux 内核提交驱动程序
-=============================
-
-这篇文档将会解释如何向不同的内核源码树提交设备驱动程序。请注意,如果你感
-兴趣的是显卡驱动程序,你也许应该访问 XFree86 项目(https://www.xfree86.org/)
-和/或 X.org 项目 (https://x.org)。
-
-另请参阅 Documentation/translations/zh_CN/process/submitting-patches.rst 文档。
-
-
-分配设备号
-----------
-
-块设备和字符设备的主设备号与从设备号是由 Linux 命名编号分配权威 LANANA(
-现在是 Torben Mathiasen)负责分配。申请的网址是 https://www.lanana.org/。
-即使不准备提交到主流内核的设备驱动也需要在这里分配设备号。有关详细信息,
-请参阅 Documentation/admin-guide/devices.rst。
-
-如果你使用的不是已经分配的设备号,那么当你提交设备驱动的时候,它将会被强
-制分配一个新的设备号,即便这个设备号和你之前发给客户的截然不同。
-
-设备驱动的提交对象
-------------------
-
-Linux 2.0:
-       此内核源码树不接受新的驱动程序。
-
-Linux 2.2:
-       此内核源码树不接受新的驱动程序。
-
-Linux 2.4:
-       如果所属的代码领域在内核的 MAINTAINERS 文件中列有一个总维护者,
-       那么请将驱动程序提交给他。如果此维护者没有回应或者你找不到恰当的
-       维护者,那么请联系 Willy Tarreau <[email protected]>。
-
-Linux 2.6:
-       除了遵循和 2.4 版内核同样的规则外,你还需要在 linux-kernel 邮件
-       列表上跟踪最新的 API 变化。向 Linux 2.6 内核提交驱动的顶级联系人
-       是 Andrew Morton <[email protected]>。
-
-决定设备驱动能否被接受的条件
-----------------------------
-
-许可:            代码必须使用 GNU 通用公开许可证 (GPL) 提交给 Linux,但是
-               我们并不要求 GPL 是唯一的许可。你或许会希望同时使用多种
-               许可证发布,如果希望驱动程序可以被其他开源社区(比如BSD)
-               使用。请参考 include/linux/module.h 文件中所列出的可被
-               接受共存的许可。
-
-版权:            版权所有者必须同意使用 GPL 许可。最好提交者和版权所有者
-               是相同个人或实体。否则,必需列出授权使用 GPL 的版权所有
-               人或实体,以备验证之需。
-
-接口:            如果你的驱动程序使用现成的接口并且和其他同类的驱动程序行
-               为相似,而不是去发明无谓的新接口,那么它将会更容易被接受。
-               如果你需要一个 Linux 和 NT 的通用驱动接口,那么请在用
-               户空间实现它。
-
-代码:            请使用 Documentation/process/coding-style.rst 中所描述的 Linux 代码风
-               格。如果你的某些代码段(例如那些与 Windows 驱动程序包共
-               享的代码段)需要使用其他格式,而你却只希望维护一份代码,
-               那么请将它们很好地区分出来,并且注明原因。
-
-可移植性:  请注意,指针并不永远是 32 位的,不是所有的计算机都使用小
-               尾模式 (little endian) 存储数据,不是所有的人都拥有浮点
-               单元,不要随便在你的驱动程序里嵌入 x86 汇编指令。只能在
-               x86 上运行的驱动程序一般是不受欢迎的。虽然你可能只有 x86
-               硬件,很难测试驱动程序在其他平台上是否可用,但是确保代码
-               可以被轻松地移植却是很简单的。
-
-清晰度:   做到所有人都能修补这个驱动程序将会很有好处,因为这样你将
-               会直接收到修复的补丁而不是 bug 报告。如果你提交一个试图
-               隐藏硬件工作机理的驱动程序,那么它将会被扔进废纸篓。
-
-电源管理:  因为 Linux 正在被很多移动设备和桌面系统使用,所以你的驱
-               动程序也很有可能被使用在这些设备上。它应该支持最基本的电
-               源管理,即在需要的情况下实现系统级休眠和唤醒要用到的
-               .suspend 和 .resume 函数。你应该检查你的驱动程序是否能正
-               确地处理休眠与唤醒,如果实在无法确认,请至少把 .suspend
-               函数定义成返回 -ENOSYS(功能未实现)错误。你还应该尝试确
-               保你的驱动在什么都不干的情况下将耗电降到最低。要获得驱动
-               程序测试的指导,请参阅
-               Documentation/power/drivers-testing.rst。有关驱动程序电
-               源管理问题相对全面的概述,请参阅
-               Documentation/driver-api/pm/devices.rst。
-
-管理:            如果一个驱动程序的作者还在进行有效的维护,那么通常除了那
-               些明显正确且不需要任何检查的补丁以外,其他所有的补丁都会
-               被转发给作者。如果你希望成为驱动程序的联系人和更新者,最
-               好在代码注释中写明并且在 MAINTAINERS 文件中加入这个驱动
-               程序的条目。
-
-不影响设备驱动能否被接受的条件
-------------------------------
-
-供应商:   由硬件供应商来维护驱动程序通常是一件好事。不过,如果源码
-               树里已经有其他人提供了可稳定工作的驱动程序,那么请不要期
-               望“我是供应商”会成为内核改用你的驱动程序的理由。理想的情
-               况是:供应商与现有驱动程序的作者合作,构建一个统一完美的
-               驱动程序。
-
-作者:            驱动程序是由大的 Linux 公司研发还是由你个人编写,并不影
-               响其是否能被内核接受。没有人对内核源码树享有特权。只要你
-               充分了解内核社区,你就会发现这一点。
-
-
-资源列表
---------
-
-Linux 内核主源码树:
-       ftp.??.kernel.org:/pub/linux/kernel/...
-       ?? == 你的国家代码,例如 "cn"、"us"、"uk"、"fr" 等等
-
-Linux 内核邮件列表:
-       [email protected]
-       [可通过向[email protected]发邮件来订阅]
-
-Linux 设备驱动程序,第三版(探讨 2.6.10 版内核):
-       https://lwn.net/Kernel/LDD3/ (免费版)
-
-LWN.net:
-       每周内核开发活动摘要 - https://lwn.net/
-
-       2.6 版中 API 的变更:
-
-               https://lwn.net/Articles/2.6-kernel-api/
-
-       将旧版内核的驱动程序移植到 2.6 版:
-
-               https://lwn.net/Articles/driver-porting/
-
-内核新手(KernelNewbies):
-       为新的内核开发者提供文档和帮助
-       https://kernelnewbies.org/
-
-Linux USB项目:
-       http://www.linux-usb.org/
-
-写内核驱动的“不要”(Arjan van de Ven著):
-       http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf
-
-内核清洁工 (Kernel Janitor):
-       https://kernelnewbies.org/KernelJanitors
--

2.17.1

#13 lore raw

PATCH 11/11 docs: zh_TW: align to submitting-drivers removal

In reply to Lukas Bulwahn

Adjust the Taiwanese translation to the removal of submitting-drivers in the English kernel documentation.

---
 .../translations/zh_TW/process/5.Posting.rst  |   3 +-
 .../translations/zh_TW/process/howto.rst      |   1 -
 .../translations/zh_TW/process/index.rst      |   1 -
 .../zh_TW/process/submitting-drivers.rst      | 164 ------------------
 4 files changed, 1 insertion(+), 168 deletions(-)
 delete mode 100644 Documentation/translations/zh_TW/process/submitting-drivers.rst
Documentation/translations/zh_TW/process/5.Posting.rst +1 -2
index 5578bca403e6..280a8832ecc0 100644
@@ -22,8 +22,7 @@
 內核開發社區已經發展出一套用於發布補丁的約定和過程;遵循這些約定和過程將使
 參與其中的每個人的生活更加輕鬆。本文檔試圖描述這些約定的部分細節;更多信息
 也可在以下文檔中找到
-:ref:`Documentation/translations/zh_TW/process/submitting-patches.rst <tw_submittingpatches>`,
-:ref:`Documentation/translations/zh_TW/process/submitting-drivers.rst <tw_submittingdrivers>`
+:ref:`Documentation/translations/zh_TW/process/submitting-patches.rst <tw_submittingpatches>`
 和 :ref:`Documentation/translations/zh_TW/process/submit-checklist.rst <tw_submitchecklist>`。
 
 何時郵寄
Documentation/translations/zh_TW/process/howto.rst +0 -1
index 2043691b92e3..68ae4411285b 100644
@@ -99,7 +99,6 @@ Linux內核代碼中包含有大量的文檔。這些文檔對於學習如何與
     的代碼。
 
   :ref:`Documentation/translations/zh_TW/process/submitting-patches.rst <tw_submittingpatches>`
-  :ref:`Documentation/process/submitting-drivers.rst <submittingdrivers>`
 
     這兩份文檔明確描述如何創建和發送補丁,其中包括(但不僅限於):
        - 郵件內容
Documentation/translations/zh_TW/process/index.rst +0 -1
index ec7ad14bfd13..c5c59b4fd595 100644
@@ -43,7 +43,6 @@
 .. toctree::
    :maxdepth: 1
 
-   submitting-drivers
    submit-checklist
    stable-api-nonsense
    stable-kernel-rules
Documentation/translations/zh_TW/process/submitting-drivers.rst deleted +0 -164

164 lines not on this page · raw message

Signature · 1 line
2.17.1
maintainer
#14 lore raw
In reply to Lukas Bulwahn
Quoted 5 lines · Lukas Bulwahn

Dear Jonathan, dear Federico, dear Alex, dear Yanteng, dear Hu,

Here is an attempt to delete submitting-drivers with some improvements and clean-up in other documentation places to convince ourselves that nothing valuable is lost when deleting this checklist.

So my purpose today was to go ahead and apply these patches, but ...

Quoted 12 lines

Patch 1, 2 and 3 is just basic clean-up before adding a new reference (see Patch 4). Patch 4 adds the one reference from submitting-drivers, not already mentioned elsewhere in the repository. Patch 5 updates a confusing statement in devices.rst from earlier .txt/.tex distinction times to the new state now with Sphinx & .rst.

Patch 6 finally deletes the outdated document, with a cross-check what is covered elsewhere and few open questions (see below).

Patch 7 and 8 have been reworked with the native-speaking doc maintainers; they cause no new warnings and are ready to pick,

Quoted 8 lines

Patch 9 to 11 are weak attempts to adjust the translation, but they need to be taken further by others due to my lack of knowledge on the other languages. They would currently also cause new warnings in the doc-build right now. They should not be picked if there is no one to continue to adjust the text and fix the warnings on broken references.

I hope that patches 1 to 8 can be picked into doc-next, and then we see how to fix up the translations as well.

...even if I do that I get warnings:

Documentation/translations/zh_CN/process/howto.rst:98: WARNING:
undefined label: submittingdrivers (if the link has no caption the label must precede a section header)

it's actually better if I apply the full series, but there's still a few of them. I *really* don't want to add more warnings to the docs build, so I've backed off for now.

Alex, can you fix the remaining references in zh_CN?

For zh_TW I'm wondering ... that is increasingly looking like an unmaintained drive-by submission. I suppose we can just brute-force remove the references, but I once again find myself wondering about the value of this translation. Is there anybody out there who cares about it who could fix this up properly?

Thanks,

jon

#15 lore raw
Quoted 7 lines

Alex, can you fix the remaining references in zh_CN?

For zh_TW I'm wondering ... that is increasingly looking like an unmaintained drive-by submission. I suppose we can just brute-force remove the references, but I once again find myself wondering about the value of this translation. Is there anybody out there who cares about it who could fix this up properly?

Hi Jon,

Both zh_CN and zh_TW were fixed on
https://lore.kernel.org/linux-doc/[email protected]/T/#u

Sorry for the issue

Thanks
Alex

maintainer
#16 lore raw
Quoted 8 lines · Alex Shi
Quoted 7 lines

Alex, can you fix the remaining references in zh_CN?

For zh_TW I'm wondering ... that is increasingly looking like an unmaintained drive-by submission. I suppose we can just brute-force remove the references, but I once again find myself wondering about the value of this translation. Is there anybody out there who cares about it who could fix this up properly?

Quoted 6 lines

Hi Jon,

Both zh_CN and zh_TW were fixed on
https://lore.kernel.org/linux-doc/[email protected]/T/#u

Sorry for the issue

No worries, thanks for dealing with it. That did the trick, and the series is now applied.

Thanks,

jon