Re: [PATCH] Documentation/RCU: Fix minor typo

On Tue, Oct 18, 2016 at 12:43:24AM -0700, Josh Triplett wrote: > On Tue, Oct 18, 2016 at 12:54:03AM -0400, Pranith Kumar wrote: > > deference should actually be dereference. > > > > Signed-off-by: Pranith Kumar > > Good catch. > > Reviewed-by: Josh Triplett

Re: The downside of math::

Hi Jon, Em Wed, 19 Oct 2016 17:02:46 -0600 Jonathan Corbet escreveu: > Hey, Mauro, > > So I was a little surprised to find that the htmldocs build now breaks on > one of my machines due to a lack of LaTeX. A bit of digging turned up > the culprit: commit b7ff94df5628

Re: The downside of math::

Em Wed, 19 Oct 2016 22:26:18 -0200 Mauro Carvalho Chehab escreveu: > Hi Jon, > > Em Wed, 19 Oct 2016 17:02:46 -0600 > Jonathan Corbet escreveu: > > > Hey, Mauro, > > > > So I was a little surprised to find that the htmldocs build now breaks on > >

Re: [RESEND PATCH v2 4/4] usb: doc: add document for USB3 debug port usage

Hi Jani, On 10/19/2016 03:48 PM, Jani Nikula wrote: > On Wed, 19 Oct 2016, Lu Baolu wrote: >> Add Documentation/usb/usb3-debug-port.txt. This document includes >> the user guide for USB3 debug port. > If you're adding completely new files, please at least consider

Re: [PATCH v2 16/37] Documentation/module-signing.txt: convert to ReST markup

Em Wed, 19 Oct 2016 06:58:12 +0200 Markus Heiser escreveu: > just a small suggestion of mine > > .. CONTENTS > > - Overview. > - Configuring module signing. > - Generating signing keys. > - Public keys in the kernel. > - Manually signing modules. >

Re: [PATCH v2 16/37] Documentation/module-signing.txt: convert to ReST markup

Am 19.10.2016 um 11:33 schrieb Mauro Carvalho Chehab : > Em Wed, 19 Oct 2016 06:58:12 +0200 > Markus Heiser escreveu: > >> just a small suggestion of mine >> >> .. CONTENTS >> >> - Overview. >> - Configuring module signing. >> -

[PATCH 1/2] hwmon: (mcp3021) rework for DT support

Support setting the reference voltage from the device tree. Rework of driver structure, put chip specific data in a separate structure and assign it depending on device id from platform data or DT match. Extend the device documentation and also change S_IRUGO to the better readable 0444, which

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

Em Wed, Oct 19, 2016 at 12:01:26PM +0200, Peter Zijlstra escreveu: > On Tue, Oct 18, 2016 at 05:15:01PM -0400, Daniel Micay wrote: > > It's also worth noting that fine-grained control via a scoped mechanism > > would likely only be used to implement *more restrictions* on Android, > > not to make

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

On Mon, Oct 17, 2016 at 10:54:33AM -0400, Daniel Micay wrote: > On Mon, 2016-10-17 at 14:44 +0100, Mark Rutland wrote: > > It's also my understanding that for Android, perf_event_paranoid is > > lowered when the user enables developer mode (rather than only when an > > external debugger is

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

On Wed, 2016-10-19 at 07:26 -0300, Arnaldo Carvalho de Melo wrote: > > But self profiling JITs would be useful for non-developers, on Android > (anywhere, really), and for that it would require being able to at > least, well, self profile, using sys_perf_event_open() by a normal > process,

Re: sequence diagrams in rst documentation

On Tue, 2016-10-18 at 17:52 -0600, Jonathan Corbet wrote: > In summary, I think we can consider taking on a module if it's what > we need to do the docs right.  And if somebody agrees to maintain it! > :) :) I think for the ones that we carry, they're probably specific? > I've heard others say

Re: sequence diagrams in rst documentation

On Wed, 19 Oct 2016, Markus Heiser wrote: > Am 18.10.2016 um 16:52 schrieb Jani Nikula : > >>> *Only* adding the PNG would be awful, I'd have to keep track of the >>> corresponding source elsewhere, and perhaps couldn't even GPL it >>>

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

On Wed, 2016-10-19 at 10:41 +0100, Mark Rutland wrote: > On Mon, Oct 17, 2016 at 10:54:33AM -0400, Daniel Micay wrote: > > On Mon, 2016-10-17 at 14:44 +0100, Mark Rutland wrote: > > > It's also my understanding that for Android, perf_event_paranoid > > > is > > > lowered when the user enables

Re: [PATCH v20 10/10] fpga-manager: Add Socfpga Arria10 support

On Tue, 18 Oct 2016, Moritz Fischer wrote: > On Mon, Oct 17, 2016 at 11:09:41AM -0500, Alan Tull wrote: > > Add low level driver to support reprogramming FPGAs for Altera > > SoCFPGA Arria10. > > > > Signed-off-by: Alan Tull > > Reviewed-by: Moritz Fischer

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

On Wed, Oct 19, 2016 at 07:26:02AM -0300, Arnaldo Carvalho de Melo wrote: > Em Wed, Oct 19, 2016 at 12:01:26PM +0200, Peter Zijlstra escreveu: > > On Tue, Oct 18, 2016 at 05:15:01PM -0400, Daniel Micay wrote: > > > It's also worth noting that fine-grained control via a scoped mechanism > > > would

Re: sequence diagrams in rst documentation

Am 18.10.2016 um 16:52 schrieb Jani Nikula : >> *Only* adding the PNG would be awful, I'd have to keep track of the >> corresponding source elsewhere, and perhaps couldn't even GPL it >> because then I couldn't distribute the PNG without corresponding >> source... >>

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

On Tue, Oct 18, 2016 at 05:15:01PM -0400, Daniel Micay wrote: > It's also worth noting that fine-grained control via a scoped > mechanism would likely only be used to implement *more restrictions* > on Android, not to make the feature less aggressive. It's desirable > for perf events to be

Re: [PATCH 00/32] Create an User's manual and improve development-process book

Em Tue, 18 Oct 2016 17:25:42 -0600 Jonathan Corbet escreveu: > On Tue, 18 Oct 2016 08:20:18 -0200 > Mauro Carvalho Chehab wrote: > > > > While at it, how about unifying some of the FilenamesInCamelCase, > > > filenames-with-hyphens, and

Re: [RESEND PATCH v2 4/4] usb: doc: add document for USB3 debug port usage

On Wed, 19 Oct 2016, Lu Baolu wrote: > Add Documentation/usb/usb3-debug-port.txt. This document includes > the user guide for USB3 debug port. If you're adding completely new files, please at least consider writing them in reStructuredText, so we can easily bolt them to

Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open

On Tue, Oct 18, 2016 at 05:15:01PM -0400, Daniel Micay wrote: > It's also worth noting that fine-grained control via a scoped mechanism > would likely only be used to implement *more restrictions* on Android, > not to make the feature less aggressive. > It's desirable for perf events to be

[PATCH v2 2/3] workqueue: kerneldocify workqueue_attrs

Only formating changes. Signed-off-by: Silvio Fricke --- include/linux/workqueue.h | 30 +- 1 file changed, 21 insertions(+), 9 deletions(-) diff --git a/include/linux/workqueue.h b/include/linux/workqueue.h index fc6e221..afc1d46 100644 ---

[PATCH v2 0/3] workqueue documentation reformatted

Hi, Thanks Jani for reviewing of my first attempt. v1 -> v2: * s/kernel-doc: $type_param takes care that this parameter is used for formatting too. * i/l/workqueue.h: inlining of documentation for workqueue_attrs struct members * D/workqueue.rst: Every author get a own :AUTHOR:-label *

[PATCH v2 1/3] kernel-doc: better parsing of named variable arguments

Without this patch we get warnings for named variable arguments. warning: No description found for parameter '...' warning: Excess function parameter 'args' description in 'alloc_ordered_workqueue' Signed-off-by: Silvio Fricke --- scripts/kernel-doc | 8

Re: [PATCH v2 3/3] Documentation/workqueue.txt: convert to ReST markup

On Wed, Oct 19, 2016 at 08:38:39PM +0200, Silvio Fricke wrote: > This patch add a "misc" documentation section and add the workqueue > documentation to this section. > > Signed-off-by: Silvio Fricke Looks good to me. How should these patches be routed? Should I take 2

[PATCH] Documentation/sphinx: rename kernel-doc.py to kerneldoc.py

Python module names should not have hyphens per [PEP 8]. Drop the hyphen from kernel-doc.py. The extension directive remains unchanged. [PEP 8] https://www.python.org/dev/peps/pep-0008/#package-and-module-names Reported-by: Markus Heiser Signed-off-by: Jani Nikula

miss some documentation on https://www.kernel.org/doc/

Hi kernel.org maintainers, sorry for my silly question: I miss the documentation of the reST (sphinx) content [1] on https://www.kernel.org/doc/ Since the DocBook files migrated to reST (sphinx) increase the "htmldocs" at [3] are decreasing. I suppose you build HTML of the DocBook content of [3]

Re: [PATCH] Documentation/sphinx: rename kernel-doc.py to kerneldoc.py

Am 19.10.2016 um 12:44 schrieb Jani Nikula : > Python module names should not have hyphens per [PEP 8]. Drop the hyphen > from kernel-doc.py. The extension directive remains unchanged. > > [PEP 8] https://www.python.org/dev/peps/pep-0008/#package-and-module-names > >