[PATCH v3 07/21] Documentation/CodingStyle: Convert to ReST markup

- Fix all chapter identation; - add c blocks where needed; Signed-off-by: Mauro Carvalho Chehab --- Documentation/CodingStyle | 253 ++ 1 file changed, 187 insertions(+), 66 deletions(-) diff --git

[PATCH v3 01/21] doc: development-process: convert it to ReST markup

This document is on good shape for ReST: all it was needed was to fix the section markups, add a toctree, convert the tables and add a few code/quote blocks. While not strictly required, I opted to use lowercase for the titles, just like the other books that were converted to Sphinx.

[PATCH v3 17/21] Documentation/SubmittingPatches: convert it to ReST markup

- Change the sections to use ReST markup; - Add cross-references where needed; - convert aspas to verbatim text; - use code block tags; - make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab --- Documentation/SubmittingPatches | 233

[PATCH v3 19/21] docs-rst: move HOWTO and mentioned documents to development-process/

In preparation to add those files to the Sphinx build logic, move them to development-process/ dir and rename their extension to RST. Please notice that the main README file was not moved. It probably makes sense to move it too as well, in order to be able to parse it via Sphinx, but this could

[PATCH v3 14/21] Documentation/stable_api_nonsense.txt: convert it to ReST markup

Add markups for it to be properly parsed by Sphinx. As people browsing this document may not notice that the source file title is "stable_api_nonsense", I opted to use bold to the rationale for this document. I also found it better to add a note when it says that the nonsense applies only to the

[PATCH v3 15/21] Documentation/stable_kernel_rules.txt: convert it to ReST markup

- use ReST markups for section headers; - add cross-references to the options; - mark code blocks; - a few minor changes to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab --- Documentation/stable_kernel_rules.txt | 101 +++--- 1

[PATCH v3 05/21] Documentation/applying-patches.txt: convert it to ReST markup

- use the correct markup to identify each section; - Add some blank lines for Sphinx to properly interpret the markups; - Remove a blank space on some paragraphs; - Fix the verbatim and bold markups; - Cleanup the remaining errors to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab

[PATCH v3 16/21] Documentation/SubmittingDrivers: convert it to ReST markup

- Change the document title markup to make it on a higher level; - Add blank lines as needed, to improve the output; - use italics for the country-code at kernel.org ftp URL. Signed-off-by: Mauro Carvalho Chehab --- Documentation/SubmittingDrivers | 45

Re: [RFC PATCH 00/11] pci: support for configurable PCI endpoint

On Wednesday, September 14, 2016 10:41:56 AM CEST Kishon Vijay Abraham I wrote: > This patch series > *) adds PCI endpoint core layer > *) modifies designware/dra7xx driver to be configured in EP mode > *) adds a PCI endpoint *test* function driver Hi Kishon, I think this is a

[PATCH v3 08/21] Documentation/CodingStyle: use the proper tag for verbatim font

On Sphinx/ReST notation, ``foo`` means that foo will be displayed using a monospaced font. As we want this document to be parsed by Sphinx, instead of using "foo", use ``foo`` for the names that are literal, because it is an usual typographic convention to use monospaced fonts for functions and

[PATCH v3 21/21] doc-rst: Add the new development-process/ files to Sphinx build

Include the new files under Documentation/development-process/ to the toctree, for them to be used by Sphinx. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/index.rst | 13 + 1 file changed, 13 insertions(+) diff --git

[PATCH v3 18/21] Documentation/HOWTO: add cross-references to other documents

Add cross references for the documents mentioned at HOWTO and are under the Documentation/ directory, using the ReST notation. It should be noticed that HOWTO also mentions the /README file. We opted to not touch it, for now, as making it build on Sphinx would require it to be moved to a

[PATCH v3 13/21] Documentation/SecurityBugs: convert it to ReST markup

Add a name for the document and convert the sections to ReST markups. Signed-off-by: Mauro Carvalho Chehab --- Documentation/SecurityBugs | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/Documentation/SecurityBugs

[PATCH v3 04/21] Documentation/HOWTO: convert to ReST notation

This document is almost compliant with ReST notation, but some small adjustments are needed to make it parse properly by Sphinx (mostly, add blank lines where needed). Signed-off-by: Mauro Carvalho Chehab --- Documentation/HOWTO | 53

Re: [PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

Am 14.09.2016 um 11:35 schrieb Mauro Carvalho Chehab : > Em Wed, 14 Sep 2016 09:45:10 +0200 > Jean Delvare escreveu: > >> On Tue, 13 Sep 2016 16:24:48 -0300, Mauro Carvalho Chehab wrote: >>> Em Tue, 13 Sep 2016 19:45:23 +0200 >>> Jean Delvare

Re: [PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

Em Wed, 14 Sep 2016 14:18:55 +0200 Markus Heiser escreveu: > Am 14.09.2016 um 11:35 schrieb Mauro Carvalho Chehab > : > > > Em Wed, 14 Sep 2016 09:45:10 +0200 > > Jean Delvare escreveu: > > > >> On Tue, 13 Sep 2016

Re: [PATCH 00/17] Create a book for Kernel development

Hi Jon, Em Mon, 12 Sep 2016 10:40:41 -0600 Jonathan Corbet escreveu: > On Mon, 12 Sep 2016 11:47:51 -0300 > Mauro Carvalho Chehab wrote: > > - Some of this will need wider exposure for a different reason: I suspect > there will be resistance to

[PATCH v3 09/21] Documentation/CodingStyle: replace underline markups

Sphinx doesn't accept underline markups by purpose. While there are ways to support underline via CSS, this won't be portable with non-html outputs. As we want CodingStyle to do emphasis, replace _foo_ by **foo**, using bold emphasis. Signed-off-by: Mauro Carvalho Chehab

[PATCH v3 10/21] Documentation/CodingStyle: use the .. note:: markup where needed

There are two places there where there are notes that should be highlighted. So, use the ReST note markup for such texts. Signed-off-by: Mauro Carvalho Chehab --- Documentation/CodingStyle | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git

[PATCH v3 00/21] Create a book for Kernel development

That's the third version of this series. Version 1 was submitted to linux-doc only. There are several documents related to Kernel development, where the HOWTO works like an index to several such documents. There are also a series of files describing the development process. This patch series:

Re: [PATCH v2 0/6] Move runnable code (tests) from Documentation to selftests

On Tue, 13 Sep 2016 14:18:39 -0600 Shuah Khan wrote: > Move runnable code (tests) from Documentation to selftests and update > Makefiles to work under selftests. This all seems good to me. Acked-by: Jonathan Corbet jon -- To unsubscribe from this

Re: [RFC PATCH v2 14/20] x86: DMA support for memory encryption

On 09/12/2016 05:58 AM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:38:07PM -0500, Tom Lendacky wrote: >> Since DMA addresses will effectively look like 48-bit addresses when the >> memory encryption mask is set, SWIOTLB is needed if the DMA mask of the >> device performing the DMA does

[PATCH v3 03/21] docs-rst: create a book for the development process

Now that the files at Documentation/development-process/ were converted to ReST, make create a book at Sphinx. As we'll have other books related to the development process, we'll add it as a sub-book. Signed-off-by: Mauro Carvalho Chehab --- Documentation/conf.py

Re: [RFC PATCH v2 15/20] iommu/amd: AMD IOMMU support for memory encryption

On 09/12/2016 06:45 AM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:38:20PM -0500, Tom Lendacky wrote: >> Add support to the AMD IOMMU driver to set the memory encryption mask if >> memory encryption is enabled. >> >> Signed-off-by: Tom Lendacky >> --- >>

Re: [RFC PATCH v2 11/20] mm: Access BOOT related data in the clear

On 09/12/2016 11:55 AM, Andy Lutomirski wrote: > On Aug 22, 2016 6:53 PM, "Tom Lendacky" wrote: >> >> BOOT data (such as EFI related data) is not encyrpted when the system is >> booted and needs to be accessed as non-encrypted. Add support to the >> early_memremap API to

Re: [RFC PATCH v2 20/20] x86: Add support to make use of Secure Memory Encryption

On 09/12/2016 12:08 PM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:39:08PM -0500, Tom Lendacky wrote: >> This patch adds the support to check if SME has been enabled and if the >> mem_encrypt=on command line option is set. If both of these conditions >> are true, then the encryption mask

Re: [RFC PATCH v2 10/20] x86: Insure that memory areas are encrypted when possible

On 09/12/2016 11:33 AM, Borislav Petkov wrote: > On Mon, Sep 12, 2016 at 10:05:36AM -0500, Tom Lendacky wrote: >> I can look into that. The reason I put this here is this is all the >> early page fault support that is very specific to this file. I modified >> an existing static function to take

Re: [RFC PATCH v2 15/20] iommu/amd: AMD IOMMU support for memory encryption

On Wed, Sep 14, 2016 at 08:45:44AM -0500, Tom Lendacky wrote: > Currently, mem_encrypt.h only lives in the arch/x86 directory so it > wouldn't be able to be included here without breaking other archs. I'm wondering if it would be simpler to move only sme_me_mask to an arch-agnostic header just so

Re: [RFC PATCH v2 18/20] x86/kvm: Enable Secure Memory Encryption of nested page tables

On 09/12/2016 09:35 AM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:38:49PM -0500, Tom Lendacky wrote: >> Update the KVM support to include the memory encryption mask when creating >> and using nested page tables. >> >> Signed-off-by: Tom Lendacky >> --- >>

Re: [RFC PATCH v2 16/20] x86: Check for memory encryption on the APs

On 09/12/2016 11:43 AM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:38:29PM -0500, Tom Lendacky wrote: >> Add support to check if memory encryption is active in the kernel and that >> it has been enabled on the AP. If memory encryption is active in the kernel > > A small nit: let's

Re: [RFC PATCH v2 19/20] x86: Access the setup data through debugfs un-encrypted

On Wed, Sep 14, 2016 at 09:29:41AM -0500, Tom Lendacky wrote: > This is still required because just using the __va() would still cause > the mapping created to have the encryption bit set. The ioremap call > will result in the mapping not having the encryption bit set. I meant this:

Re: [PATCH] scsi: replace broken specification URL

> "Michael" == Michael Opdenacker > writes: Michael> So, should we only that the cam-r12b document can be found from Michael> http://www.t10.org/t10docs.htm (registration required)?, and Michael> tell that a copy can be found on Michael>

Re: [PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

Am 14.09.2016 um 15:48 schrieb Mauro Carvalho Chehab : > Em Wed, 14 Sep 2016 14:18:55 +0200 > Markus Heiser escreveu: > >> Am 14.09.2016 um 11:35 schrieb Mauro Carvalho Chehab >> : >> >>> Em Wed, 14 Sep 2016

[PATCH RESEND] crypto: doc - fix documentation for bulk registration functions

Update the documentation for crypto_register_algs() and crypto_unregister_algs() to match the actual behavior. Signed-off-by: Eric Biggers --- Documentation/DocBook/crypto-API.tmpl | 38 --- 1 file changed, 26 insertions(+), 12 deletions(-)

[PATCH v2 1/3] drivers/of: recognize status property of dt memory nodes

Respect the standard dt "status" property when scanning memory nodes in early_init_dt_scan_memory(), so that if the property is present and not "okay", no memory will be added. The use case at hand is accelerator or device memory, which may be unusable until post-boot initialization of the memory

[PATCH v2 3/3] mm: enable CONFIG_MOVABLE_NODE on powerpc

Onlining memory into ZONE_MOVABLE requires CONFIG_MOVABLE_NODE. Enable the use of this config option on PPC64 platforms. Signed-off-by: Reza Arbab --- Documentation/kernel-parameters.txt | 2 +- mm/Kconfig | 2 +- 2 files changed, 2

[PATCH v2 2/3] powerpc/mm: allow memory hotplug into a memoryless node

Remove the check which prevents us from hotplugging into an empty node. This limitation has been questioned before [1], and judging by the response, there doesn't seem to be a reason we can't remove it. No issues have been found in light testing. [1]

[PATCH v2 0/3] powerpc/mm: movable hotplug memory nodes

These changes enable onlining memory into ZONE_MOVABLE on power, and the creation of discrete nodes of movable memory. We provide a way to describe the extents and numa associativity of such a node in the device tree, yet still defer the memory addition to take place post-boot through hotplug.

[PATCH 01/17] HOWTO.rst: update information about generating documentation

The description there are pre-Sphinx. Update it to cover the new way. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/HOWTO.rst | 28 ++-- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git

[PATCH 12/17] SubmittingPatches.rst: enrich the Sphinx output

Do a few changes to make the output look better: - use bullets on trivial patches list; - use monotonic font for tools name; - use :manpage:`foo` for man pages; - don't put all references to maintainer*html at the same line. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 17/17] applying-patches.rst: Update the information there

This document is old: it is from Kernel v2.6.12 days. Update it to the current status, and add a reference for the linux-next tree. Signed-off-by: Mauro Carvalho Chehab --- .../development-process/applying-patches.rst | 255 + 1 file changed,

[PATCH 03/17] HOWTO.rst: adjust external link references

- A few link references were missing http:// - Several sites are now redirecting to https protocol. On such cases, just use the https URL. NOTE: all URLs were checked and they're pointing to the right places. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 14/17] stable_api_nonsense.rst: fix emphasis on Sphinx

Unfortunately, Sphinx doesn't have a way to use underlines. So, let's replace _any_ by **any**. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/stable_api_nonsense.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 00/17] Improve documentation for the development-process

This patch series is a followup to be applied after the: [PATCH v3 00/21] Create a book for Kernel development patch series. It addresses some issues I noticed after re-reading the html docs after the conversion of those files to ReST. It also converts two extra documents to ReST:

[PATCH 05/17] SubmitChecklist: update kernel-doc task

Task 11 (kernel-doc) still mentions usage of make manpages, but this won't work if the API is documented via Sphinx. So, update it to use either htmldocs or pdfdocs, with are the documentation targets that work for all. While here, add ReST reference to the kernel documentation book.

[PATCH 04/17] Changes.rst: add minimal requirements for documentation build

As discussed at linux-doc ML, the best is to keep all documents backward compatible with Sphinx version 1.2, as it is the latest version found on some distros like Debian. All books currently support it. Please notice that, while it mentions the eventual need of XeLaTex and texlive to build pdf

Re: [PATCHv12 1/3] rdmacg: Added rdma cgroup controller

Hi Dennis, Do you know how would HFI1 driver would work along with rdma cgroup? Hi Matan, Leon, Jason, Apart from HFI1, is there any other concern? Or Patch is good to go? 4.8 dates are close by (2 weeks) and there are two git trees involved (that might cause merge error to Linus) so if there

Re: [PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

Em Wed, 14 Sep 2016 09:45:10 +0200 Jean Delvare escreveu: > On Tue, 13 Sep 2016 16:24:48 -0300, Mauro Carvalho Chehab wrote: > > Em Tue, 13 Sep 2016 19:45:23 +0200 > > Jean Delvare escreveu: > > > > > Hi Mauro, > > > > > > On Mon, 12 Sep 2016 11:47:57

Re: [PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

On Tue, 13 Sep 2016 16:24:48 -0300, Mauro Carvalho Chehab wrote: > Em Tue, 13 Sep 2016 19:45:23 +0200 > Jean Delvare escreveu: > > > Hi Mauro, > > > > On Mon, 12 Sep 2016 11:47:57 -0300, Mauro Carvalho Chehab wrote: > > > Instead of using "foo", use ``foo`` for the names that

Re: [PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

Am 14.09.2016 um 09:45 schrieb Jean Delvare : > On Tue, 13 Sep 2016 16:24:48 -0300, Mauro Carvalho Chehab wrote: >> Em Tue, 13 Sep 2016 19:45:23 +0200 >> Jean Delvare escreveu: >> >>> Hi Mauro, >>> >>> On Mon, 12 Sep 2016 11:47:57 -0300, Mauro Carvalho

Re: [PATCH v5 0/3] mm, proc: Implement /proc//totmaps

On Tue 13-09-16 13:27:39, Sonny Rao wrote: > On Tue, Sep 13, 2016 at 12:12 AM, Michal Hocko wrote: > > On Mon 12-09-16 10:28:53, Sonny Rao wrote: > >> On Mon, Sep 12, 2016 at 10:15 AM, Michal Hocko wrote: > >> > On Mon 12-09-16 08:31:36, Sonny Rao wrote: > >

Re: [PATCHv12 1/3] rdmacg: Added rdma cgroup controller

On 14/09/2016 10:06, Parav Pandit wrote: Hi Dennis, Do you know how would HFI1 driver would work along with rdma cgroup? Hi Matan, Leon, Jason, Apart from HFI1, is there any other concern? I just wonder how things like RSS will work. For example, a RSS QP doesn't really have a queue (if I

[PATCH V2 2/2] cpufreq: Add android's 'interactive' governor

Interactive governor has lived in Android sources for a very long time and this commit is based on the code present in following branch: https://android.googlesource.com/kernel/common android-4.4 The Interactive governor is designed for latency-sensitive workloads, such as interactive user

[PATCH 15/17] ManagementStyle.rst: avoid emphasis where not desired

On Spinx, anything like: foo bar will output **foo** in bold. We don't want that on this text. So, add an extra line. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/ManagementStyle.rst | 2 ++ 1 file changed, 2 insertions(+) diff

[PATCH 16/17] stable_kernel_rules.rst: Add cross-references to other ReST files

Add two references for files that were already converted to ReST. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/stable_kernel_rules.rst | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

[PATCH 09/17] email-clients.txt: convert it to ReST markup

As this file is mentioned at the development-process/ book, let's convert it to ReST markup. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/5.Posting.rst| 2 +- .../development-process/SubmittingPatches.rst | 2 +-

[PATCH 10/17] email-clients.txt: add it to the development-process book

This file is mentioned inside SubmittingPatches, and it is related to the patch submission process. So, move it to the right book, making Sphinx build it. Signed-off-by: Mauro Carvalho Chehab --- .../{email-clients.txt => development-process/email-clients.rst}

[PATCH 13/17] SubmittingDrivers.rst: add a cross reference to CodingStyle

Instead of mentioning CodingStyle as a file, use a reference. While here, do a minor update, pointing that the same rules for Kernel 2.6 apply up to the recent versions too. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 02/17] HOWTO.rst: improve some markups to make it visually better

Do a series of minor improvements at the ReST output format: - Instead of using the quote blocks (::) for quotes, use italics. That looks nicer on epub (and html) output, as no scroll bar will be added. Also, it will adjust line breaks on the text automatically. - Add a missing reference to

[PATCH 11/17] SubmittingPatches.rst: Add some cross-references

This file mentions some other documents already converted to ReST format. Add cross-references for them. Signed-off-by: Mauro Carvalho Chehab --- .../development-process/SubmitChecklist.rst| 2 ++ .../development-process/SubmittingPatches.rst | 24