diff for duplicates of <20200502074133.GC342687@linux.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 37987fa..77cc972 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -51,7 +51,7 @@ Just curious, why IRQ docs got their subdirectory and DMA didn't :) > +++ b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst > @@ -10,7 +10,7 @@ them to a "housekeeping" CPU dedicated to such work. > References -> ========== +> ===== > > -- Documentation/IRQ-affinity.txt: Binding interrupts to sets of CPUs. > +- Documentation/core-api/irq/irq-affinity.rst: Binding interrupts to sets of CPUs. @@ -80,9 +80,9 @@ Just curious, why IRQ docs got their subdirectory and DMA didn't :) > --- /dev/null > +++ b/Documentation/core-api/irq/index.rst > @@ -0,0 +1,11 @@ -> +==== +> +== > +IRQs -> +==== +> +== > + > +.. toctree:: > + :maxdepth: 1 @@ -106,10 +106,8 @@ Just curious, why IRQ docs got their subdirectory and DMA didn't :) > Hierarchy irq_domain is in no way x86 specific, and is heavily used to > support other architectures, such as ARM, ARM64 etc. > -> -=== Debugging === -> +Debugging -> +========= -> +> -== Debugging => +Debugging +> +====> > Most of the internals of the IRQ subsystem are exposed in debugfs by > turning CONFIG_GENERIC_IRQ_DEBUGFS on. > diff --git a/Documentation/irqflags-tracing.txt b/Documentation/core-api/irq/irqflags-tracing.rst diff --git a/a/content_digest b/N1/content_digest index 94e3625..30d6d86 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,7 +2,7 @@ "ref\02da7485c3718e1442e6b4c2dd66857b776e8899b.1588345503.git.mchehab+huawei@kernel.org\0" "From\0Mike Rapoport <rppt@linux.ibm.com>\0" "Subject\0Re: [PATCH 07/14] docs: add IRQ documentation at the core-api book\0" - "Date\0Sat, 2 May 2020 10:41:33 +0300\0" + "Date\0Sat, 02 May 2020 07:41:33 +0000\0" "To\0Mauro Carvalho Chehab <mchehab+huawei@kernel.org>\0" "Cc\0Linux Doc Mailing List <linux-doc@vger.kernel.org>" linux-kernel@vger.kernel.org @@ -81,7 +81,7 @@ "> +++ b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst\n" "> @@ -10,7 +10,7 @@ them to a \"housekeeping\" CPU dedicated to such work.\n" "> References\n" - "> ==========\n" + "> =====\n" "> \n" "> --\tDocumentation/IRQ-affinity.txt: Binding interrupts to sets of CPUs.\n" "> +-\tDocumentation/core-api/irq/irq-affinity.rst: Binding interrupts to sets of CPUs.\n" @@ -110,9 +110,9 @@ "> --- /dev/null\n" "> +++ b/Documentation/core-api/irq/index.rst\n" "> @@ -0,0 +1,11 @@\n" - "> +====\n" + "> +==\n" "> +IRQs\n" - "> +====\n" + "> +==\n" "> +\n" "> +.. toctree::\n" "> + :maxdepth: 1\n" @@ -136,10 +136,8 @@ "> Hierarchy irq_domain is in no way x86 specific, and is heavily used to\n" "> support other architectures, such as ARM, ARM64 etc.\n" "> \n" - "> -=== Debugging ===\n" - "> +Debugging\n" - "> +=========\n" - "> \n" + "> -== Debugging => +Debugging\n" + "> +====> \n" "> Most of the internals of the IRQ subsystem are exposed in debugfs by\n" "> turning CONFIG_GENERIC_IRQ_DEBUGFS on.\n" "> diff --git a/Documentation/irqflags-tracing.txt b/Documentation/core-api/irq/irqflags-tracing.rst\n" @@ -221,4 +219,4 @@ "Sincerely yours,\n" Mike. -19643b5463e4428ca22f2fc38dc71bf93dc42a83cd208d72f2d5118879e86701 +2496815f5aba585bfd65841d89cdcee7f248ca739fbd6a570222359d4fa5276e
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.