[PATCH v2 0/4] crypto: async crypto op fixes

This patch set fixes various usage and documentation errors in waiting for async crypto op to complete which can result in data corruption. Note: these were discovered in the process of working on a patch set that replaces these call sites and more with a generic implementation that will prevent

[PATCH v2] kexec/kdump: Minor Documentation updates for arm64 and Image

This patch have minor updates in Documentation for arm64i as relocatable kernel. Also this patch updates documentation for using uncompressed image "Image" which is used for ARM64. Signed-off-by: Bharat Bhushan --- v1->v2 - "a uncompressed" replaced with "an

[PATCH v2 3/4] crypto: gcm wait for crypto op not signal safe

crypto_gcm_setkey() was using wait_for_completion_interruptible() to wait for completion of async crypto op but if a signal occurs it may return before DMA ops of HW crypto provider finish, thus corrupting the data buffer that is kfree'ed in this case. Resolve this by using wait_for_completion()

[PATCH v7 1/2] init: add support to directly boot to a mapped device

From: Will Drewry Add a dm= kernel parameter modeled after the md= parameter from do_mounts_md. It allows for device-mapper targets to be configured at boot time for use early in the boot process (as the root device or otherwise). Signed-off-by: Will Drewry

[PATCH v7 2/2] dm ioctl: add a device mapper ioctl function.

Add a dm_ioctl_cmd to issue the equivalent of a DM ioctl call in kernel. Signed-off-by: Enric Balletbo i Serra --- drivers/md/dm-ioctl.c | 45 +++ include/linux/device-mapper.h | 6 ++ 2 files changed, 51

Re: [PATCH] core-api: remove an unexpected unident

On Sat, 13 May 2017 15:28:25 +0200 Markus Heiser wrote: > As complained by Sphinx: > Documentation/core-api/assoc_array.rst:13: WARNING: Enumerated list > ends without a blank line; unexpected unindent. > > This was already addressed, but not really fixed in

[RFC PATCH] mm, oom: cgroup-aware OOM-killer

Traditionally, the OOM killer is operating on a process level. Under oom conditions, it finds a process with the highest oom score and kills it. This behavior doesn't suit well the system with many running containers. There are two main issues: 1) There is no fairness between containers. A small

Re: [PATCH] Documentation, kbuild: fix typo "minimun" -> "minimum"

On Thu, 18 May 2017 14:17:29 +0200 Tobias Klauser wrote: > Documentation/kbuild/makefiles.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/kbuild/makefiles.txt > b/Documentation/kbuild/makefiles.txt > index

Re: [RFC PATCH v2 10/17] cgroup: Make debug cgroup support v2 and thread mode

On 05/17/2017 05:43 PM, Tejun Heo wrote: > Hello, > > On Mon, May 15, 2017 at 09:34:09AM -0400, Waiman Long wrote: >> Besides supporting cgroup v2 and thread mode, the following changes >> are also made: >> 1) current_* cgroup files now resides only at the root as we don't >> need duplicated

Re: [PATCH 00/17] convert/reorganize Documentation/security/

On Sat, 13 May 2017 04:51:36 -0700 Kees Cook wrote: > This ReSTifies everything under Documentation/security/, and reorganizes > some of it (mainly the LSMs) under /admin-guide/ per Jon's request. Since > /security/ is already being indexed under the kernel development

Re: [RFC PATCH v2 11/17] cgroup: Implement new thread mode semantics

On 05/17/2017 05:47 PM, Tejun Heo wrote: > Hello, Waiman. > > On Mon, May 15, 2017 at 09:34:10AM -0400, Waiman Long wrote: >> The current thread mode semantics aren't sufficient to fully support >> threaded controllers like cpu. The main problem is that when thread >> mode is enabled at root

Re: [RFC PATCH] mm, oom: cgroup-aware OOM-killer

On Thu 18-05-17 17:28:04, Roman Gushchin wrote: > Traditionally, the OOM killer is operating on a process level. > Under oom conditions, it finds a process with the highest oom score > and kills it. > > This behavior doesn't suit well the system with many running > containers. There are two main

Re: [PATCH] doc-rst: fix inline emphasis in unshare.rst

On Sat, 13 May 2017 15:41:38 +0200 Markus Heiser wrote: > The asterisk of the pointer is interpreted as a start tag for inline > emphasis. Asterisks which are not Sphinx markup need to be quoted in > rst-files. This fixes the Sphinx warning: > >

Re: [PATCH 00/17] convert/reorganize Documentation/security/

On Thu, May 18, 2017 at 9:49 AM, Jonathan Corbet wrote: > On Sat, 13 May 2017 04:51:36 -0700 > Kees Cook wrote: > >> This ReSTifies everything under Documentation/security/, and reorganizes >> some of it (mainly the LSMs) under /admin-guide/ per Jon's

Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption

On Tue, Apr 18, 2017 at 04:22:12PM -0500, Tom Lendacky wrote: > Add sysfs support for SME so that user-space utilities (kdump, etc.) can > determine if SME is active. But why do user-space tools need to know that? I mean, when we load the kdump kernel, we do it with the first kernel, with the

[PATCH v2 4/4] crypto: Documentation: fix none signal safe sample

The sample code was showing use of wait_for_completion_interruptible() for waiting for an async. crypto op to finish. However, if a signal arrived it would free the buffers used even while crypto HW might still DMA from/into the buffers. Resolve this by using wait_for_completion() instead.

Re: [RFC PATCH] mm, oom: cgroup-aware OOM-killer

On Fri, May 19, 2017 at 04:37:27AM +1000, Balbir Singh wrote: > On Fri, May 19, 2017 at 3:30 AM, Michal Hocko wrote: > > On Thu 18-05-17 17:28:04, Roman Gushchin wrote: > >> Traditionally, the OOM killer is operating on a process level. > >> Under oom conditions, it finds a

Re: [PATCH v5 17/32] x86/mm: Add support to access boot related data in the clear

On Mon, 15 May, at 08:35:17PM, Borislav Petkov wrote: > On Tue, Apr 18, 2017 at 04:19:21PM -0500, Tom Lendacky wrote: > > > + paddr = boot_params.efi_info.efi_memmap_hi; > > + paddr <<= 32; > > + paddr |= boot_params.efi_info.efi_memmap; > > + if (phys_addr

Re: [RFC PATCH] mm, oom: cgroup-aware OOM-killer

On Fri, May 19, 2017 at 3:30 AM, Michal Hocko wrote: > On Thu 18-05-17 17:28:04, Roman Gushchin wrote: >> Traditionally, the OOM killer is operating on a process level. >> Under oom conditions, it finds a process with the highest oom score >> and kills it. >> >> This behavior

Re: [RFC PATCH] mm, oom: cgroup-aware OOM-killer

On Fri, May 19, 2017 at 04:37:27AM +1000, Balbir Singh wrote: > On Fri, May 19, 2017 at 3:30 AM, Michal Hocko wrote: > > On Thu 18-05-17 17:28:04, Roman Gushchin wrote: > >> Traditionally, the OOM killer is operating on a process level. > >> Under oom conditions, it finds a

[PATCH 27/31] intel_txt.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote main title one level; - fix the bulleted list markup; - use bulletted list markup

[PATCH 24/29] vfio.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - adjust title marks; - use footnote marks; - mark literal blocks; - adjust identation.

[PATCH 29/29] dell_rbu.txt: standardize document format

From: Mauro Carvalho Chehab Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx. Currently, the document is

[PATCH 28/29] zorro.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use right marks for titles; - Use authorship marks; - Mark literals and literal blocks; -

Re: [RFC PATCH] mm, oom: cgroup-aware OOM-killer

On Thu, 2017-05-18 at 20:20 +0100, Roman Gushchin wrote: > On Fri, May 19, 2017 at 04:37:27AM +1000, Balbir Singh wrote: > > On Fri, May 19, 2017 at 3:30 AM, Michal Hocko wrote: > > > On Thu 18-05-17 17:28:04, Roman Gushchin wrote: > > > > Traditionally, the OOM killer is

[PATCH 07/29] remoteproc.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark document and section titles; - adjust identation; - mark literal blocks

[PATCH 11/29] rpmsg.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark document and chapter titles; - mark notes; - mark literal blocks; - adjust

[PATCH 19/29] svga.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use standard notation for titles; - Use the note mark; - mark literal blocks; - adjust

[PATCH 28/30] percpu-rw-semaphore.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: This document is already adopting the standard format, with a single exception: we're using

[PATCH 08/29] rfkill.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark titles; - comment contents index; - mark literal blocks; - adjust identation.

[PATCH 22/29] unaligned-memory-access.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote document title one level; - use markups for authorship and put it at the

[PATCH 15/29] siphash.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Mark titles; - Mark literal blocks; - Use :Author: for authorship; - Don't sumerate

[PATCH 21/29] this_cpu_ops.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote document title one level; - mark literal blocks; - move authorship to the

[PATCH 10/29] robust-futexes.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - add a title for the document; - mark literal blocks; Signed-off-by: Mauro Carvalho

[PATCH 16/29] SM501.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - adjust document title; - use the copyright markup. Signed-off-by: Mauro Carvalho Chehab

[PATCH 14/29] sgi-ioc4.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx. In this case, just adding a title is enough. Signed-off-by: Mauro Carvalho Chehab

[PATCH 27/29] xz.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use marks for titles; - Adjust indentation. Signed-off-by: Mauro Carvalho Chehab

[PATCH 02/29] pnp.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use a markup for document title; - use :Author: and :Last updated: for authorship; -

[PATCH 17/29] smsc_ece1099.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add a title for the document. Signed-off-by: Mauro Carvalho Chehab

[PATCH 08/30] isa.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use the main title standard for this document; - replace _foo_ by **foo** for emphasis; -

[PATCH 25/30] numastat.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark the document title; - mark the table as such. Signed-off-by: Mauro Carvalho Chehab

[PATCH 19/30] memory-barriers.txt: use literals for variables

From: Mauro Carvalho Chehab The minimal adjustments on this file were not enough to make it build clean with Sphinx: Documentation/memory-barriers.rst:192: WARNING: Inline emphasis start-string without end-string. Documentation/memory-barriers.rst:603: WARNING:

[PATCH 09/30] kernel-per-CPU-kthreads.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use title markups; - use "-" for bulletted lists; - Split Name/Purpose on two lines, in

[PATCH 05/30] irqflags-tracing.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: There isn't much to be done here: just mark the document title as such and add a :Author:.

[PATCH 23/30] nommu-mmap.txt: don't use all upper case on titles

This file is almost in the standard format we're adopting for other documentation text files. Yet, it use upper case on titles. So, in order to uniform how chapter names, adjust caps on titles. Signed-off-by: Mauro Carvalho Chehab --- Documentation/nommu-mmap.txt | 18

[PATCH 04/30] IRQ-domain.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use proper markups for titles; - mark literal blocks as such; - add blank lines where

[PATCH 07/30] isapnp.txt: promote title level

This simple document only needs to promote its title to be using the standard we're using for document texts. Yet, IMHO, it would be worth merging this file with Documentation/pnp.txt in the future. Signed-off-by: Mauro Carvalho Chehab --- Documentation/isapnp.txt | 1

[PATCH 12/30] kref.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - add a title for the document and section titles; - move authorship information to the

[PATCH 00/30] Standardize doc formats - part 2

Each document under Documentation/*.txt has its own format. Some follow markup notations, some don't even have a title! In order to try to get some order on it, change the document style to the standard we're adopting after the adoption of ReStructured Text. The documents touched on this series

[PATCH 06/30] IRQ.txt: add a markup for its title

This simple document only needs a markup for its title to be using the standard we're adopting for text documents. Signed-off-by: Mauro Carvalho Chehab --- Documentation/IRQ.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/IRQ.txt

[PATCH 15/31] DMA-API-HOWTO.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Mark titles; - Mark literal blocks; - Mark some literals that would otherwise produce

[PATCH 14/31] DMA-API.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Fix some title marks to match ReST; - use :Author: for author name; - foo_ is an

[PATCH 08/31] clk.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use section/title markups; - Use :Author: for authorship; - Mark literals and literal

[PATCH 24/31] highuid.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use a markup for the title; - use :Author: and :Last updated: markups at the beginning

[PATCH 05/31] cachetlb.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Adjust the title format; - use :Author: for author's name; - mark literals as such; - use

[PATCH 22/31] futex-requeue-pi.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote level for the document title; - mark literal blocks. Signed-off-by: Mauro

Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image

On Thu, May 18, 2017 at 01:59:14PM +0800, Dave Young wrote: > Add Takahiro and Pratyush, they should be able to review the arm64 part. > > On 05/18/17 at 11:03am, Bharat Bhushan wrote: > > This patch have minor updates in Documentation for arm64i as > > relocatable kernel. > > Also this patch

[PATCH 18/30] memory-barriers.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use (#) instead of (*) as the latter is not recognized. As a bonus, using (#) will make

[PATCH 20/29] sync_file.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use markup for document title and authorship; - Mark literal blocks; - Use a numbered list

[PATCH 25/29] video-output.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark the title; - mark the authorship; - mark literal block. Signed-off-by: Mauro

[PATCH 12/29] rtc.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - adjust identation of the titles; - mark a table as such; - don't capitalize chapter

[PATCH 09/29] robust-futex-ABI.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote document title; - use :Author: for authorship; - mark literal blocks; - add blank

[PATCH 06/29] rbtree.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Mark document title; - Use :Author: for authorship; - mark a sub-section title as such; -

[PATCH 03/29] preempt-locking.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark titles; - mark literal blocks; - adjust identation where needed; - use :Author: for

[PATCH 11/30] kprobes.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - comment the contents; - add proper markups for titles; - mark literal blocks as such; -

[PATCH 27/30] parport-lowlevel.txt: standardize document format

Each text file under Documentation follows a different format. This one uses a man-page like approach. Change its representation to be closer to the adopted standard, using ReST markups for it to be parseable by Sphinx: - Mark titles; - Mark literals and literal blocks; - Adjust identation.

[PATCH 26/30] padata.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark document title; - mark literal blocks. Signed-off-by: Mauro Carvalho Chehab

[PATCH 20/31] eisa.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use ReST notation for titles; - identify literal blocks; - use :Author: for document

[PATCH 06/31] cgroup-v2.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Comment the internal index; - Use :Date: and :Author: for authorship; - Mark titles; -

[PATCH 23/31] gcc-plugins.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote main title; - use the right markup for footnotes; - use bold markup for files

[PATCH 01/31] bcache.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add a title for the document; - Use a list for the listed URLs; - mark literal blocks; -

[PATCH 28/31] Intel-IOMMU.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: This file is almost in the right format. It only needed to convert a list to bulleted list

[PATCH 25/31] hw_random.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use proper markups for titles; - adjust section identation; - use proper markup for notes

[PATCH 23/29] vfio-mediated-device.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! In this specific document, the title, copyright and authorship are added as if it were a C file! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by

[PATCH 13/29] SAK.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark document title; - use :Author: and :Date: for authorship; - adjust notation for

[PATCH 29/30] phy.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark titles; - use :Author: for authorship; - mark literal blocks. Signed-off-by: Mauro

[PATCH 16/30] lzo.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add markups for section titles; - mark literal blocks; - use ".. important::" for an

[PATCH 00/29] Standardize doc formats - part 3

Each document under Documentation/*.txt has its own format. Some follow markup notations, some don't even have a title! In order to try to get some order on it, change the document style to the standard we're adopting after the adoption of ReStructured Text. The documents touched on this series

[PATCH 05/29] pwm.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - mark document title; - mark literal blocks; - better format the parameters.

[PATCH 24/30] ntb.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx. This file is using some other markup notation (likely, markdown). Convert it to the adopted

[PATCH 26/29] xillybus.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Adjust indentation; - Mark authorship; - Comment internal contents table; - Mark literal

[PATCH 15/30] lockup-watchdogs.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx. This file is almost at ReST format. Just one title needs to be adjusted, in order to follow

[PATCH 17/30] mailbox.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add markups for section titles; - Use :Author: for authorship; - Mark literal block as

[PATCH 22/30] nommu-mmap.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Adjust identation for main title; - fix level for chapter titles; - use ".. important::"

[PATCH 21/30] men-chameleon-bus.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Adjust identations; - Remove title numbering; - mark literal blocks; - comment its TOC.

[PATCH 30/30] pi-futex.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx. This document requires just minor adjustments to match the standard documentation style: -

[PATCH 02/30] IPMI.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - fix document type; - add missing markups for subitems; - mark literal blocks; - add

[PATCH 10/30] kobject.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add markups for titles; - mark literal blocks as such; - add needed whitespace/blank

[PATCH 01/30] iostats.txt: update it to cover recent Kernels

Everything there that it is said for 2.6 also applies on current 4.x Kernels. So, update the information there. While here, use ``foo`` for literals. Signed-off-by: Mauro Carvalho Chehab --- Documentation/iostats.txt | 44 ++--

[PATCH 13/30] kselftest.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote the level of the document title; - use literal blocks where needed; - add

[PATCH 30/31] io_ordering.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add a title; - mark literal-blocks as such. Signed-off-by: Mauro Carvalho Chehab

[PATCH 31/31] iostats.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - promote main title level; - mark literal blocks as such; - Add blank lines to avoid

[PATCH 14/30] ldm.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Reformat its title; - Use :Author: and :Last Updated: for authorship - Use note markup; -

[PATCH 16/31] DMA-attributes.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: This file is almost on the standard format. All it needs to be parsed by Sphinx is to fix

[PATCH 04/31] bus-virt-phys-mapping.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Move author info to the beginning of file and use :Author: - use warning/note annotation;

[PATCH 21/31] flexible-arrays.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use :Author: and :Updated: markups; - use proper markup for the document title; - mark

[PATCH 11/31] crc32.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Add a title for the document; - Mark literal blocks. While here, replace a comma by a

[PATCH 17/31] DMA-ISA-LPC.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - use proper markups for titles; - use :Author: for authorship; - identify the literal

[PATCH 03/31] btmrvl.txt: standardize document format

Each text file under Documentation follows a different format. Some doesn't even have titles! Change its representation to follow the adopted standard, using ReST markups for it to be parseable by Sphinx: - Use the right notation for titles; - Use a list for image names; - Use literal blocks

[PATCH v10 02/10] doc: Add documentation for Coresight CPU debug

Add detailed documentation for Coresight CPU debug driver, which contains the info for driver implementation, Mike Leach excellent summary for "clock and power domain". At the end some examples on how to enable the debugging functionality are provided. Suggested-by: Mike Leach

  1   2   >