Re: "CodingStyle: Clarify and complete chapter 7" in docs-next (was Re: [PATCH 03/47] block-rbd: Adjust the position of a jump label in rbd_header_from_disk())

On Mon, 19 Sep 2016, Joe Perches wrote: > On Tue, 2016-09-20 at 01:11 +0100, Al Viro wrote: > > IMO what we need is to go through all rules in CodingStyle and if for > > some rule there is no overwhelming majority in the core kernel, well, > > the list has grown way too large and could use

[PATCH] [linux-next] Fix double word "the the" in Doc/filesystems

This patch fix typos "the the" found in Documentation/filesystems. Signed-off-by: Masanari Iida --- Documentation/filesystems/autofs4-mount-control.txt | 10 +- Documentation/filesystems/directory-locking | 2 +- Documentation/filesystems/overlayfs.txt

Re: "CodingStyle: Clarify and complete chapter 7" in docs-next (was Re: [PATCH 03/47] block-rbd: Adjust the position of a jump label in rbd_header_from_disk())

On Tue, 2016-09-20 at 01:11 +0100, Al Viro wrote: > IMO what we need is to go through all rules in CodingStyle and if for > some rule there is no overwhelming majority in the core kernel, well, > the list has grown way too large and could use massive trimming. I'm in complete agreement. I also

Re: [PATCH 0/4] Update kernel-docs.rst

Em Tue, 20 Sep 2016 02:40:21 +0200 Richard Sailer escreveu: > I think kernel-docs.rst should be kept. (Or at least another/updated > file fullfilling this purpose should exist) Therefore I put > some effort into updating it. > > This patch relies on Mauros: >

[PATCH 0/4] Update kernel-docs.rst

I think kernel-docs.rst should be kept. (Or at least another/updated file fullfilling this purpose should exist) Therefore I put some effort into updating it. This patch relies on Mauros: [Patch v2 ...] Create a book for Kernel development Summary --- This patch: * Removes all the

[PATCH 3/4] kernel-docs.rst: Add 4 paper/book references

Background/Reasoning: Books: -- * Linux Kernel Networking by Rami Rosen While some parts are quite short and could be more carefully explained it's still a good recomendation for understanding linux kernel networking, (IMHO) * Linux Treiber entwickeln: It sure is a drawback that

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

On 2016-09-19 03:32 PM, Michal Hocko wrote: On Mon 19-09-16 11:16:31, Robert Foss wrote: On 2016-09-14 05:12 AM, Michal Hocko wrote: On Tue 13-09-16 13:27:39, Sonny Rao wrote: [...] Given that smaps doesn't provide this in a straightforward way, what do you think is the right way to

Re: "CodingStyle: Clarify and complete chapter 7" in docs-next (was Re: [PATCH 03/47] block-rbd: Adjust the position of a jump label in rbd_header_from_disk())

On Mon, Sep 19, 2016 at 01:53:37PM +0200, Ilya Dryomov wrote: > > I did consider the reason to be good enough to warrant a "change", > > actually. Or more exactly from "one space is allowed" to "one space is > > recommended." Which is quite different from changing all the code > > actively. I can

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

On Mon, Sep 19, 2016 at 12:56 PM, Jann Horn wrote: > On Mon, Sep 19, 2016 at 09:51:13PM +0200, Michal Hocko wrote: >> [not sure why the CC list was trimmed - do no do that please unless you >> have a strong reason for that - if this was not intentional please >> restpre it] > >

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

On Mon, Sep 19, 2016 at 09:51:13PM +0200, Michal Hocko wrote: > [not sure why the CC list was trimmed - do no do that please unless you > have a strong reason for that - if this was not intentional please > restpre it] Ah, sorry, pressed the wrong key. > On Mon 19-09-16 21:40:01, Jann Horn

Re: samples: move auxdisplay example code from Documentation

> Documentation/auxdisplay/cfag12864b needs to be updated to reflect the new > home for the program (which probably does belong in samples/). > > I wonder if these programs need MAINTAINERS entries too? Do you find any more update suggestions interesting around this software module?

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

On Mon 19-09-16 11:16:31, Robert Foss wrote: > On 2016-09-14 05:12 AM, Michal Hocko wrote: > > On Tue 13-09-16 13:27:39, Sonny Rao wrote: [...] > > > Given that smaps > > > doesn't provide this in a straightforward way, what do you think is > > > the right way to provide this information? > > > >

[git:media_tree/master] MAINTAINERS: update documentation for media subsystem

This is an automatic generated email to let you know that the following patch were queued: Subject: MAINTAINERS: update documentation for media subsystem Author: Mauro Carvalho Chehab Date:Mon Sep 12 12:48:54 2016 -0300 With ReST conversion, the media subsystem

Re: [PATCH] [media] videodev2.h.rst.exceptions: fix warnings

On 09/19/2016 07:32 PM, Mauro Carvalho Chehab wrote: > Changeset ab6343956f9c ("[media] V4L2: Add documentation for SDI timings > and related flags") added documentation for new V4L2 defines, but > it forgot to update videodev2.h.rst.exceptions to point to where > the documentation for those new

[PATCH] [media] videodev2.h.rst.exceptions: fix warnings

Changeset ab6343956f9c ("[media] V4L2: Add documentation for SDI timings and related flags") added documentation for new V4L2 defines, but it forgot to update videodev2.h.rst.exceptions to point to where the documentation for those new values will be inside the book, causing those warnings:

Re: [PATCH 6/8] samples: move pcmcia example code from Documentation

On Mon, 19 Sep 2016 08:47:37 -0600 Shuah Khan wrote: > Move pcmcia examples to samples and remove it from Documentation > Makefile. Create a new Makefile to build pcmcia. It can be built > from top level directory or from pcmcia directory: Does PCMCIA still exist/work?

Re: [PATCH 5/8] samples: move misc-devices/mei example code from Documentation

On Mon, 19 Sep 2016 08:47:36 -0600 Shuah Khan wrote: > Move misc-devices/mei examples to samples/mei and remove it from > Documentation Makefile. Delete misc-devices/Makefile. > > Create a new Makefile to build samples/mei. It can be built from top > level directory or

Re: [PATCH 4/8] samples: move mic/mpssd example code from Documentation

On Mon, 19 Sep 2016 08:47:35 -0600 Shuah Khan wrote: > Move mic/mpssd examples to samples and remove it from Documentation > Makefile. Create a new Makefile to build mic/mpssd. It can be built > from top level directory or from mic/mpssd directory: > > Run make -C

Re: [PATCH 3/8] samples: move laptops example code from Documentation

On Mon, 19 Sep 2016 08:47:34 -0600 Shuah Khan wrote: > Move laptops examples to samples and remove it from Documentation > Makefile. Create a new Makefile to build laptops. It can be built > from top level directory or from laptops directory: This one might be better

Re: [PATCH 2/8] samples: move auxdisplay example code from Documentation

On Mon, 19 Sep 2016 08:47:33 -0600 Shuah Khan wrote: > Move auxdisplay examples to samples and remove it from Documentation > Makefile. Create a new Makefile to build auxdisplay. It can be built > from top level directory or from auxdisplay directory:

Re: [PATCH 1/8] samples: move accounting example code from Documentation

On Mon, 19 Sep 2016 08:47:32 -0600 Shuah Khan wrote: > Move accounting examples to samples and remove it from Documentation > Makefile. Create a new Makefile to build accounting. It can be built > from top level directory or from accounting directory: So I like the

Re: [PATCH 0/8] Move runnable examples code from Documentation to samples

On Mon, 19 Sep 2016, Shuah Khan wrote: > Move runnable examples code from Documentation to samples. I moved > just the example code, and left documentation files as is. FWIW I like this. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe

Re: [PATCH v2 0/3] doc-rst:c-domain: fix some issues in the c-domain

Em Mon, 19 Sep 2016 13:36:55 +0200 Markus Heiser escreveu: > Hi Mauro, > > sorry for my late reply (so much work to do) .. > > Am 09.09.2016 um 14:25 schrieb Markus Heiser : > > >> Using either this approach or my kernel-doc patch, I'm

[PATCH 1/8] samples: move accounting example code from Documentation

Move accounting examples to samples and remove it from Documentation Makefile. Create a new Makefile to build accounting. It can be built from top level directory or from accounting directory: Run make -C samples/accounting or cd samples/accounting; make Signed-off-by: Shuah Khan

[PATCH 6/8] samples: move pcmcia example code from Documentation

Move pcmcia examples to samples and remove it from Documentation Makefile. Create a new Makefile to build pcmcia. It can be built from top level directory or from pcmcia directory: Run make -C samples/pcmcia or cd samples/pcmcia; make Signed-off-by: Shuah Khan ---

[PATCH 3/8] samples: move laptops example code from Documentation

Move laptops examples to samples and remove it from Documentation Makefile. Create a new Makefile to build laptops. It can be built from top level directory or from laptops directory: Run make -C samples/laptops or cd samples/laptops; make Signed-off-by: Shuah Khan ---

[PATCH 5/8] samples: move misc-devices/mei example code from Documentation

Move misc-devices/mei examples to samples/mei and remove it from Documentation Makefile. Delete misc-devices/Makefile. Create a new Makefile to build samples/mei. It can be built from top level directory or from mei directory: Run make -C samples/mei or cd samples/mei; make Signed-off-by: Shuah

[PATCH 8/8] samples: move watchdog example code from Documentation

Move watchdog examples to samples and remove it from Documentation Makefile. Create a new Makefile to build watchdog. It can be built from top level directory or from watchdog directory: Run make -C samples/watchdog or cd samples/watchdog; make Signed-off-by: Shuah Khan

[PATCH 7/8] samples: move timers example code from Documentation

Move timers examples to samples and remove it from Documentation Makefile. Create a new Makefile to build timers. It can be built from top level directory or from timers directory: Run make -C samples/timers or cd samples/timers; make Signed-off-by: Shuah Khan ---

[PATCH 2/8] samples: move auxdisplay example code from Documentation

Move auxdisplay examples to samples and remove it from Documentation Makefile. Create a new Makefile to build auxdisplay. It can be built from top level directory or from auxdisplay directory: Run make -C samples/auxdisplay or cd samples/auxdisplay; make Signed-off-by: Shuah Khan

[PATCH 0/8] Move runnable examples code from Documentation to samples

Move runnable examples code from Documentation to samples. I moved just the example code, and left documentation files as is. blackfin gptimers example code needs a bit of special handling since it is a module. I will address it in a separate patch. 00-Index files need to be updated due to this

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

On Wed, 2016-09-14 at 12:36 +0530, Parav Pandit wrote: > Hi Dennis, > > Do you know how would HFI1 driver would work along with rdma cgroup? Keep in mind HFI1 driver has two "modes" of operation. We support verbs, and would surely fall in line with whatever cgroups do for IB core. For our psm

"CodingStyle: Clarify and complete chapter 7" in docs-next (was Re: [PATCH 03/47] block-rbd: Adjust the position of a jump label in rbd_header_from_disk())

On Mon, Sep 19, 2016 at 11:37 AM, Jean Delvare wrote: > Hi Ilya, > > Sorry for the late answer. > > On Tue, 13 Sep 2016 20:31:57 +0200, Ilya Dryomov wrote: >> Sorry, navigating lkml.org archive is a pain, and I was expecting to >> see patch. Your points >> >> "The acceptance of

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

On 15/09/16 06:06, Reza Arbab wrote: > 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. >

[PATCH v4 13/29] 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 v4 19/29] 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 | 207

[PATCH v4 22/29] 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 v4 26/29] Documentation/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 v4 23/29] Documentation/HOWTO: 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/HOWTO | 28 ++-- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/Documentation/HOWTO

[PATCH v4 28/29] Documentation/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/SubmittingPatches | 2 +- Documentation/development-process/5.Posting.rst | 2 +-

[PATCH v4 24/29] Documentation/HOWTO: 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 v4 12/29] 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 v4 07/29] Documentation/applying-patches.txt: 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 --- Documentation/applying-patches.txt | 255 - 1 file changed,

[PATCH v4 02/29] 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 v4 25/29] Documentation/HOWTO: 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 v4 27/29] Documentation/SubmitChecklist: convert it to ReST markup

- use ``foo`` to markup inline literal stuff, effectively making it to be presented as a monospaced font when parsed by Sphinx; - the markup below the title should have the same length as the title; - Fix the list markups, from "1:" to "1)"; - Split item 2 into a separate list for the build

[PATCH v4 10/29] Documentation/CodingStyle: Convert to ReST markup

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

[PATCH v4 14/29] Documentation/ManagementStyle: convert it to ReST markup

- Convert document name to ReST; - Convert footnotes; - Convert sections to ReST format; - Don't use _foo_, as Sphinx doesn't support underline. Instead, use bold; - While here, remove whitespaces at the end of lines. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH v4 15/29] 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 | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/SecurityBugs b/Documentation/SecurityBugs index

[PATCH v4 11/29] Documentation/CodingStyle: use the proper tag for verbatim font

On Sphinx/ReST notation, ``foo`` means that foo will be will be marked as inline literal, effectively making it to be presented as 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

[PATCH v4 17/29] 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 v4 16/29] 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 v4 18/29] 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

[PATCH v4 09/29] Documentation/Changes: 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

[PATCH v4 04/29] 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

[PATCH v4 06/29] 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 v4 05/29] 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

[PATCH v4 00/29] Create a book for Kernel development

That's the 4th version of this series. It also contains a second patch series with more ReST conversions and documentation improvements. This patchset merges the content of a second patch series: [PATCH 00/17] Improve documentation for the development-process I opted to keep the patch

[PATCH v4 08/29] Documentation/Changes: convert it to ReST markup

- Fix chapter identation inconsistencies; - Convert table to ReST format; - use the right tag for bullets; - Fix bold emphasis; - mark blocks with :: tags; - use verbatim font for files; - make Sphinx happy Signed-off-by: Mauro Carvalho Chehab --- Documentation/Changes

[PATCH v4 01/29] doc-rst: add CSS styles for :kbd: and :menuselection:

As we're about to use those two markups, add them to the theme style overrride. Signed-off-by: Mauro Carvalho Chehab --- Documentation/sphinx-static/theme_overrides.css | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git

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

On 15/09/16 06:06, Reza Arbab wrote: > 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 >

Re: pyc files in source dir with O=

On Sun, 18 Sep 2016, Markus Heiser wrote: > Am 07.09.2016 um 15:28 schrieb Jani Nikula : > >> On Wed, 07 Sep 2016, Geert Uytterhoeven wrote: >>> When running "make htmldocs O=/path/to/somewhere", *.pyc files end up >>>

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

Reza Arbab writes: > 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

[PATCH v10 RESEND 2/3] Documentation: kdump: Remind user of nr_cpus

From: Zhou Wenjian nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 2 ++ 1

[PATCH v10 RESEND 1/3] docs: kernel-parameter : Improve the description of nr_cpus and maxcpus

>From the old description people still can't get what's the exact difference between nr_cpus and maxcpus. Especially in kdump kernel nr_cpus is always suggested if it's implemented in ARCH. The reason is nr_cpus is used to limit the max number of possible cpu in system, the sum of already plugged

[PATCH v10 RESEND 3/3] Documentation: kdump: Add description of enable multi-cpus support

From: Zhou Wenjian Multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He