I'm excited to see the new documentation format, so I'm changing my
documentation in the pending patches I have to use it. I however
cannot generate anything other than the main
Documentation/output/pdf/Kernel.pdf
How can I see in PDF the other documentation?
I'm using:
make DOCBOOKS="" pdfdocs
On Tue, 9 Aug 2016 01:31:06 -0700
Christoph Hellwig wrote:
> On Tue, Aug 09, 2016 at 10:28:38AM +0200, Daniel Vetter wrote:
> > The point is to make the docs more discoverable by being able to
> > cross-link them. Old hats like us don't need that, but it definitely
> > has value in bringing new f
Here is a respin of the task-isolation patch set. This primarily
reflects some testing on x86, and a rebase to 4.8.
I have been getting email asking me when and where this patch will be
upstreamed so folks can start using it. I had been thinking the
obvious path was via Frederic Weisbecker to In
This commit adds support for tracking asynchronous interrupts
delivered to task-isolation tasks, e.g. IPIs or IRQs. Just
as for exceptions and syscalls, when this occurs we arrange to
deliver a signal to the task so that it knows it has been
interrupted. If the task is interrupted by an NMI, we c
By default, if a task in task isolation mode re-enters the kernel,
it is terminated with SIGKILL. With this commit, the application
can choose what signal to receive on a task isolation violation
by invoking prctl() with PR_TASK_ISOLATION_ENABLE, or'ing in the
PR_TASK_ISOLATION_USERSIG bit, and se
The existing nohz_full mode is designed as a "soft" isolation mode
that makes tradeoffs to minimize userspace interruptions while
still attempting to avoid overheads in the kernel entry/exit path,
to provide 100% kernel semantics, etc.
However, some applications require a "hard" commitment from th
This option, similar to NO_HZ_FULL_ALL, simplifies configuring
a system to boot by default with all cores except the boot core
running in task isolation mode.
Signed-off-by: Chris Metcalf
---
init/Kconfig | 10 ++
kernel/isolation.c | 6 ++
2 files changed, 16 insertions(+)
d
Am 09.08.2016 um 20:02 schrieb Mauro Carvalho Chehab :
> Em Tue, 9 Aug 2016 09:21:08 -0600
> Jonathan Corbet escreveu:
>
>> On Mon, 8 Aug 2016 15:14:57 +0200
>> Markus Heiser wrote:
>>
>>> this is my approach for a more generic way to build only sphinx
>>> sub-folders, we
>>> discussed in [
Em Tue, 9 Aug 2016 09:21:08 -0600
Jonathan Corbet escreveu:
> On Mon, 8 Aug 2016 15:14:57 +0200
> Markus Heiser wrote:
>
> > this is my approach for a more generic way to build only sphinx
> > sub-folders, we
> > discussed in [1]. The last patch adds a minimal conf.py to the gpu folder,
> >
Add descriptions for dax, io_poll, and write_same_max_bytes files.
Signed-off-by: Joe Lawrence
---
Documentation/block/queue-sysfs.txt | 18 ++
1 file changed, 18 insertions(+)
diff --git a/Documentation/block/queue-sysfs.txt
b/Documentation/block/queue-sysfs.txt
index d515d589
On Mon, 8 Aug 2016 15:14:57 +0200
Markus Heiser wrote:
> this is my approach for a more generic way to build only sphinx sub-folders,
> we
> discussed in [1]. The last patch adds a minimal conf.py to the gpu folder, if
> you don't want to patch the gpu folder drop it.
I haven't had a chance to
From: Thor Thayer
Add the device tree entries needed to support the Altera SD/MMC
FIFO buffer EDAC on the Arria10 chip.
Signed-off-by: Thor Thayer
Acked-by: Dinh Nguyen
---
v2 No change
---
arch/arm/boot/dts/socfpga_arria10_socdk_sdmmc.dts | 12
1 file changed, 12 insertions(+
From: Thor Thayer
Add the SD/MMC FIFO EDAC module which is a dual-port RAM as
opposed to the other Arria10 peripheral's single port RAM FIFOs.
Thor Thayer (3):
Documentation: dt: socfpga: Add Arria10 SD-MMC EDAC binding
EDAC, altera: Add Arria10 SD-MMC EDAC support
ARM: dts: Add Arria10 SD
From: Thor Thayer
Add Altera Arria10 SD-MMC FIFO memory EDAC support. The SD-MMC
is a dual port RAM implementation which is different than any
of the other peripherals and therefore requires additional code.
Signed-off-by: Thor Thayer
---
v2 Cleanup PortB initialization by moving device tree s
From: Thor Thayer
Add the device tree bindings needed to support the Altera SD-MMC
FIFO buffers EDAC on the Arria10 chip.
Signed-off-by: Thor Thayer
Acked-by: Rob Herring
---
v2 No change
---
.../bindings/arm/altera/socfpga-eccmgr.txt | 19 +++
1 file changed, 19 in
Move the documentation into Documentation/gpu, link it up and pull in
the kernel doc.
No actual text changes except that I did polish the kerneldoc a bit,
especially for vga_client_register().
v2: Remove some rst from vga-switcheroo.rst that I don't understand,
but which seems to be the reason wh
Le 09/08/16 à 01:34, Jonathan Corbet a écrit :
No textual changes have been made, but the formatting has obviously been
tweaked.
Cc: Michal Marek
Cc: Gilles Muller
Cc: Nicolas Palix
Cc: Julia Lawall
Signed-off-by: Jonathan Corbet
Acked-by: Nicolas Palix
---
.../{coccinelle.txt => dev-
Move the documentation into Documentation/gpu, link it up and pull in
the kernel doc.
No actual text changes except that I did polish the kerneldoc a bit,
especially for vga_client_register().
v2: Remove some rst from vga-switcheroo.rst that I don't understand,
but which seems to be the reason wh
These are the leftovers I could only track down using keep_warnings =
True. For some of them we might want to update our style guide on how
to reference structures and constants, not sure ...
Cc: Markus Heiser
Cc: Jonathan Corbet
Cc: linux-doc@vger.kernel.org
Signed-off-by: Daniel Vetter
---
d
First part is just a bit of rst fallout to make drm doc builds warning free. But
then I started to split out parts of drm_crtc into their own files. framebuffers
and connectors are done, next up on my plans are encoders, and then the base
stuff around drm_mode_object, properties and blobs. I think
On Tue, Aug 9, 2016 at 10:31 AM, Christoph Hellwig wrote:
> On Tue, Aug 09, 2016 at 10:28:38AM +0200, Daniel Vetter wrote:
>> The point is to make the docs more discoverable by being able to
>> cross-link them. Old hats like us don't need that, but it definitely
>> has value in bringing new folks
On Tue, Aug 9, 2016 at 1:34 AM, Jonathan Corbet wrote:
> No textual changes beyond formatting.
>
> Cc: Andrey Ryabinin
> Cc: Alexander Potapenko
> Cc: Dmitry Vyukov
> Signed-off-by: Jonathan Corbet
Acked-by: Alexander Potapenko
> ---
> Documentation/dev-tools/kasan.rst | 173
> +
On Tue, 09 Aug 2016, Jonathan Corbet wrote:
> This series of patches collects a number of documents related to kernel
> development tools, converts them to the Sphinx format, and puts them
> together into the dev-tools directory. The resulting formatted
> documentation can be seen at:
>
> h
On Tue, Aug 09, 2016 at 10:28:38AM +0200, Daniel Vetter wrote:
> The point is to make the docs more discoverable by being able to
> cross-link them. Old hats like us don't need that, but it definitely
> has value in bringing new folks on board.
But do that in a way that keeps the old hats happy.
On Tue, Aug 9, 2016 at 10:22 AM, Christoph Hellwig wrote:
> On Tue, Aug 09, 2016 at 11:19:50AM +0300, Jani Nikula wrote:
>> On Tue, 09 Aug 2016, Christoph Hellwig wrote:
>> > The ugly format is a major regression over a proper simple text
>> > file. What's the point?
>>
>> Major regression? Plea
On Tue, Aug 09, 2016 at 11:19:50AM +0300, Jani Nikula wrote:
> On Tue, 09 Aug 2016, Christoph Hellwig wrote:
> > The ugly format is a major regression over a proper simple text
> > file. What's the point?
>
> Major regression? Please be reasonable.
>
> I think the changes are rather small, and
On Tue, 09 Aug 2016, Christoph Hellwig wrote:
> The ugly format is a major regression over a proper simple text
> file. What's the point?
Major regression? Please be reasonable.
I think the changes are rather small, and it's a fair compromise between
a simple text file and one that can be used
The ugly format is a major regression over a proper simple text
file. What's the point?
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
On 9 August 2016 at 01:35, Jonathan Corbet wrote:
> +The shadow bytemap dump legend is as follows:
> +
> +- i: initialized
> +- u: uninitialized
> +- a: unallocated (memory has been allocated by the slab layer, but has not
> + yet been handed off to anybody)
> +- f: freed (memory has been al
29 matches
Mail list logo
