Re: [PATCH 0/5] Convert more books to ReST
Em Mon, 15 May 2017 14:09:12 +0200 Boris Brezillonescreveu: > On Sat, 13 May 2017 08:10:53 -0300 > Mauro Carvalho Chehab wrote: > > > This patch series convert the following books to ReST: > > - librs > > - mtdnand > > - sh > > > > And it is based on my previous series of conversion patches. > > > > After this series, there will be just one DocBook pending conversion: > > - lsm (Linux Security Modules) > > > > This book is very outdated: no changes since the Kernel moved > > to git, in 2005 (except for a minor editorial fix in 2008). > > > > I took a look on the described API: it doesn't seem to be describing > > the current security implementation. > > > > The best here is if someone that works with LSM to convert it to > > ReST with: > > $ Documentation/sphinx/tmplcvt Documentation/DocBook/lsm.tmpl lsm.rst > > > > And fix the document to produce something that reflects the current > > implementation. If nobody is interested, then maybe we could just > > drop it. > > > > - > > > > This patch series is based on my past 00/36 patch series, applied on > > the top of docs tree (next branch). > > > > The full patch series is on this tree is at: > > > >https://git.linuxtv.org//mchehab/experimental.git/log/?h=docbook > > > > And the HTML output at: > > > > http://www.infradead.org/~mchehab/kernel_docs/ > > https://mchehab.fedorapeople.org/kernel_docs/ > > > > Mauro Carvalho Chehab (5): > > docs-rst: convert librs book to ReST > > docs-rst: convert mtdnand book to ReST > > mtdnand.rst: Fix some typos and group the "::" with previous line > > MTD maintainers did not receive the above patch. Can you Cc us the > whole series next time. Sorry. I'll add you on the whole series. It will be a big one, though, as it will contain the other docbook conversions on it (~50+ patches). > BTW, I had a look at your branch and it seems the typo you're fixing is > actually not a type. Flags are *OR-ed* (with the | operator) to form a > valid combination of flags. Ah! Ok, I updated the patch (see enclosed). Would that be OK for you? > > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings > > Not sure how you plan to merge these changes, but if it goes through > a single tree I'll probably need an immutable topic branch, because I > plan to change a few things in nand_base.c nand.h for the next release. At least the patches that touch at Documentation/* should go, IMHO, via a single tree: git://git.lwn.net/linux.git docs-next As Jon mentioned, he doesn't rebase it, so you should be able to get an immutable branch from it. Thanks, Mauro --- [PATCH] mtdnand.rst: group the "::" with previous line Group the :: with the previous paragraph, in order to make it visually better when reading as a text file. While here, replace: ored (with means "Covered or adorned with ore or metal") by: OR-ed To reflect its true meaning. Signed-off-by: Mauro Carvalho Chehab diff --git a/Documentation/driver-api/mtdnand.rst b/Documentation/driver-api/mtdnand.rst index 8723175f955e..7c19795ebb4a 100644 --- a/Documentation/driver-api/mtdnand.rst +++ b/Documentation/driver-api/mtdnand.rst @@ -843,10 +843,8 @@ Chip option constants Constants for chip id table ~~~ -These constants are defined in nand.h. They are ored together to -describe the chip functionality. - -:: +These constants are defined in nand.h. They are OR-ed together to +describe the chip functionality:: /* Buswitdh is 16 bit */ #define NAND_BUSWIDTH_160x0002 @@ -867,10 +865,8 @@ describe the chip functionality. Constants for runtime options ~ -These constants are defined in nand.h. They are ored together to -describe the functionality. - -:: +These constants are defined in nand.h. They are OR-ed together to +describe the functionality:: /* The hw ecc generator provides a syndrome instead a ecc value on read * This can only work if we have the ecc bytes directly behind the @@ -881,9 +877,7 @@ describe the functionality. ECC selection constants --- -Use these constants to select the ECC algorithm. - -:: +Use these constants to select the ECC algorithm:: /* No ECC. Usage is not recommended ! */ #define NAND_ECC_NONE 0 @@ -903,9 +897,7 @@ Hardware control related constants -- These constants describe the requested hardware access function when the -boardspecific hardware control function is called - -:: +boardspecific hardware control function is called:: /* Select the chip by setting nCE to low */ #define NAND_CTL_SETNCE 1 @@ -929,9 +921,7 @@ Bad block table related constants - These constants describe the options used for bad block table -descriptors. - -:: +descriptors:: /*
Re: [PATCH 0/5] Convert more books to ReST
Hi Jonathan, On Mon, 15 May 2017 11:15:19 -0600 Jonathan Corbetwrote: > On Mon, 15 May 2017 14:09:12 +0200 > Boris Brezillon wrote: > > > > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings > > > > Not sure how you plan to merge these changes, but if it goes through > > a single tree I'll probably need an immutable topic branch, because I > > plan to change a few things in nand_base.c nand.h for the next release. > > docs-next doesn't rebase, so there shouldn't be trouble there. But we > could also just separate this patch into two pieces. I suspect we could > live with a couple of warnings for a period during the 4.13 merge window > without too much pain... I like this idea. This way I can take the nand_base.c/nand.h changes through my tree and let you pick the Doc migration bits. Thanks, Boris -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/5] Convert more books to ReST
On Mon, 15 May 2017 14:09:12 +0200 Boris Brezillonwrote: > > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings > > Not sure how you plan to merge these changes, but if it goes through > a single tree I'll probably need an immutable topic branch, because I > plan to change a few things in nand_base.c nand.h for the next release. docs-next doesn't rebase, so there shouldn't be trouble there. But we could also just separate this patch into two pieces. I suspect we could live with a couple of warnings for a period during the 4.13 merge window without too much pain... jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/5] Convert more books to ReST
On Sat, 13 May 2017 08:10:53 -0300 Mauro Carvalho Chehabwrote: > This patch series convert the following books to ReST: > - librs > - mtdnand > - sh > > And it is based on my previous series of conversion patches. > > After this series, there will be just one DocBook pending conversion: > - lsm (Linux Security Modules) > > This book is very outdated: no changes since the Kernel moved > to git, in 2005 (except for a minor editorial fix in 2008). > > I took a look on the described API: it doesn't seem to be describing > the current security implementation. > > The best here is if someone that works with LSM to convert it to > ReST with: > $ Documentation/sphinx/tmplcvt Documentation/DocBook/lsm.tmpl lsm.rst > > And fix the document to produce something that reflects the current > implementation. If nobody is interested, then maybe we could just > drop it. > > - > > This patch series is based on my past 00/36 patch series, applied on > the top of docs tree (next branch). > > The full patch series is on this tree is at: > >https://git.linuxtv.org//mchehab/experimental.git/log/?h=docbook > > And the HTML output at: > > http://www.infradead.org/~mchehab/kernel_docs/ > https://mchehab.fedorapeople.org/kernel_docs/ > > Mauro Carvalho Chehab (5): > docs-rst: convert librs book to ReST > docs-rst: convert mtdnand book to ReST > mtdnand.rst: Fix some typos and group the "::" with previous line MTD maintainers did not receive the above patch. Can you Cc us the whole series next time. BTW, I had a look at your branch and it seems the typo you're fixing is actually not a type. Flags are *OR-ed* (with the | operator) to form a valid combination of flags. > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings Not sure how you plan to merge these changes, but if it goes through a single tree I'll probably need an immutable topic branch, because I plan to change a few things in nand_base.c nand.h for the next release. > docs-rst: convert sh book to ReST > > Documentation/DocBook/Makefile |5 +- > Documentation/DocBook/librs.tmpl | 289 > Documentation/DocBook/mtdnand.tmpl | 1291 > -- > Documentation/DocBook/sh.tmpl| 105 --- > Documentation/conf.py|2 + > Documentation/core-api/index.rst |1 + > Documentation/core-api/librs.rst | 212 ++ > Documentation/driver-api/index.rst |1 + > Documentation/driver-api/mtdnand.rst | 1007 ++ > Documentation/index.rst | 11 + > Documentation/sh/index.rst | 59 ++ > drivers/mtd/nand/nand_base.c |7 +- > include/linux/mtd/nand.h |2 +- > 13 files changed, 1300 insertions(+), 1692 deletions(-) > delete mode 100644 Documentation/DocBook/librs.tmpl > delete mode 100644 Documentation/DocBook/mtdnand.tmpl > delete mode 100644 Documentation/DocBook/sh.tmpl > create mode 100644 Documentation/core-api/librs.rst > create mode 100644 Documentation/driver-api/mtdnand.rst > create mode 100644 Documentation/sh/index.rst > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html