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 a/Documentation/development-process/HOWTO.rst
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:
Do
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.
Signed-off-b
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 f
- 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
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
---
.../development-process/Submi
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, 110 insertions(+), 145 dele
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 a/Documentation/development-process
- 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
---
Documentation/development-process/HOWTO.rst
Add it to the development-process book, by renaming it to
SubmitChecklist.rst and move it to the development-process
directory.
Signed-off-by: Mauro Carvalho Chehab
---
.../{SubmitChecklist => development-process/SubmitChecklist.rst} | 2 +-
Documentation/development-process/index.rst
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} | 0
Documentation/developm
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 --git a/Documentation/devel
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 a/Documentation/development-process/stable_kernel_rules.rs
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 +-
Documentation/email-clients.txt
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 Submi
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 ++
.../develo
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 a/Documentation/sphinx-static/theme_overrides
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
---
Documentation/development-process/SubmittingDrivers.rst | 7 ---
1 file chan
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.
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]
http://lkml.kernel.org/r/cagzkibrmksa1yyhbf5h
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
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 insertions(+), 2 deletions(-)
diff --
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(-)
diff --git a/Documenta
> "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>
http://www.csit-sun.pub.ro/~cpop/Documentatie_SMP
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 09:45:10 +0200
>>> Jean Delvare escreveu:
>>>
On Tue, 13 Sep 2016 16:24:48 -03
On Wed, 14 Sep 2016 10:48:33 -0300, Mauro Carvalho Chehab wrote:
> Ok, what about using this comment for the patch?
>
> 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 maki
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: https://lkml.k
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
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 i
On 09/12/2016 11:59 AM, Borislav Petkov wrote:
> On Mon, Aug 22, 2016 at 05:38:59PM -0500, Tom Lendacky wrote:
>> Since the setup data is in memory in the clear, it must be accessed as
>> un-encrypted. Always use ioremap (similar to sysfs setup data support)
>> to map the data.
>>
>> Signed-off-by
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 identify the type of data
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 write
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 ad
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
>> ---
>> arch/x86/include/asm/kvm_host.h
On 09/12/2016 07:17 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
>> but has not been enabled on
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 16:24:48 -0300, Mauro Carvalho Chehab wrote:
> >>> Em Tue, 13 Sep 2016 19:
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
>> ---
>> arch/x86/include/asm/mem_encrypt.
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 list: send the line "unsubscribe linux-doc" in
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 not
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 g
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 escreveu:
>>>
Hi Mauro,
On Mon, 12
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 a/Documentation/CodingStyl
Now that the documents were converted, rename them to .rst, as
this is needed by the Sphinx build logic.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/development-process/{1.Intro => 1.Intro.rst}| 0
Documentation/development-process/{2.Process => 2.Process.rst}
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:
1)
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 la
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 a/Documentation/development-process/
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
---
Documentation/Codin
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 b/Documentation/SecurityBugs
index a660d494c8ed..5
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 Documenta
- 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 | 224
- 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
---
Documentation/ManagementStyle | 152
- 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 a/Documentation/CodingStyle b/Documentation/CodingSty
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.
Signed-off-b
- 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 file changed, 68 insertions(+)
- 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
-
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 be
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
k
- 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 -
- 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 +++-
1 file changed, 13
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 +
1 file
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 | 2 ++
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 renaming well-known documents like
> Submitti
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 -0300, Mauro Carvalho Chehab wrote:
>
Hi Matan,
On Wed, Sep 14, 2016 at 1:44 PM, Matan Barak wrote:
> 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
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:
> > [...]
> >> >> but how about the other
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 interf
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 re
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 Chehab wrote:
Instead of using "foo"
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 are
> > > literal.
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 ar
70 matches
Mail list logo
