Re: [RFC] Tools to fix/prevent broken Documentation file references

Quoting Jani Nikula (2018/01/16 04:03:13 -0500) > Related, see scripts/documentation-file-ref-check. Thanks for the pointer. So perhaps (an updated version of) the script I gave originally could be put there. But doesn't seem there's much interest in it, at least for the time being. Genki -- To

Re: [PATCH v3] input: pxrc: new driver for PhoenixRC Flight Controller Adapter

On Wed, Jan 17, 2018 at 02:58:40PM +0100, Marcus Folkesson wrote: > Hello Dmitry, > > On Tue, Jan 16, 2018 at 03:16:25PM -0800, Dmitry Torokhov wrote: > > Hi Marcus, > > > > On Sat, Jan 13, 2018 at 09:15:32PM +0100, Marcus Folkesson wrote: > > > This driver let you plug in your RC controller to

Re: [PATCH v2 3/7] soc: qcom: Add GENI based QUP Wrapper driver

On Thu, Jan 18, 2018 at 08:57:45AM -0800, Bjorn Andersson wrote: > On Thu 18 Jan 01:13 PST 2018, Rajendra Nayak wrote: > > > [].. > > > > >> diff --git a/drivers/soc/qcom/qcom-geni-se.c > > >> b/drivers/soc/qcom/qcom-geni-se.c > > >> new file mode 100644 > > >> index 000..3f43582 > > >> ---

Re: [PATCH v2 2/7] dt-bindings: soc: qcom: Add device tree binding for GENI SE

On Tue, Jan 16, 2018 at 10:25:58PM -0800, Bjorn Andersson wrote: > On Fri 12 Jan 17:05 PST 2018, Karthikeyan Ramasubramanian wrote: > > > Add device tree binding support for the QCOM GENI SE driver. > > > > Signed-off-by: Karthikeyan Ramasubramanian > > Better describe

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

On Wed, 17 Jan 2018, David Rientjes wrote: > Yes, this is a valid point. The policy of "tree" and "all" are identical > policies and then the mechanism differs wrt to whether one process is > killed or all eligible processes are killed, respectively. My motivation > for this was to avoid

Re: [PATCH v2 0/7] Introduce GENI SE Controller Driver

On 01/12/2018 05:05 PM, Karthikeyan Ramasubramanian wrote: > Generic Interface (GENI) firmware based Qualcomm Universal Peripheral (QUP) > Wrapper is a next generation programmable module for supporting a wide > range of serial interfaces like UART, SPI, I2C, I3C, etc. A single QUP > module can

Re: [RESEND PATCH v8 5/5] document: add document for kaslr_mem

On 01/18/2018 09:23 PM, Chao Fan wrote: > Cc: linux-doc@vger.kernel.org > Cc: Jonathan Corbet > Cc: Randy Dunlap > Signed-off-by: Chao Fan > --- > Documentation/admin-guide/kernel-parameters.txt | 10 ++ > 1 file changed,

Re: [RESEND PATCH] Documentation: input: ff: fix small typos

On Thu, Jan 18, 2018 at 04:49:03PM -0500, Jean-François Têtu wrote: > Fix small typos in the Instructions and Uploading sections. Fix a typo in > the start/stop effect example usage code. > > Signed-off-by: Jean-François Têtu Applied, thank you. > --- >

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

Ram Pai writes: > On Fri, Jan 19, 2018 at 10:09:41AM -0600, Eric W. Biederman wrote: >> Ram Pai writes: >> >> > Currently the architecture specific code is expected to >> > display the protection keys in smap for a given vma. >> > This can lead

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

On Fri, Jan 19, 2018 at 10:09:41AM -0600, Eric W. Biederman wrote: > Ram Pai writes: > > > Currently the architecture specific code is expected to > > display the protection keys in smap for a given vma. > > This can lead to redundant code and possibly to divergent >

[PATCH] Mention kernel-doc Context section

From: Matthew Wilcox The scripts/kernel-doc processor mentions the ability to add arbitrary section names and suggests including a Context: section. We already have about 450 Context: sections in the kernel, so document it. We also have around 250 Locking: sections in

Re: [PATCH v10 27/27] mm: display pkey in smaps if arch_pkeys_enabled() is true

Ram Pai writes: > Currently the architecture specific code is expected to > display the protection keys in smap for a given vma. > This can lead to redundant code and possibly to divergent > formats in which the key gets displayed. > > This patch changes the

[PATCH 1/1] Documentation: clk: enable lock is not held for clk_is_enabled API

The core does not need to hold enable lock for clk_is_enabled API. Update the doc to reflect it. Cc: Jonathan Corbet Cc: Stephen Boyd Suggested-by: Stephen Boyd Signed-off-by: Dong Aisheng ---

Re: kernel.org documentation link (was Re: Protecting code integrity with PGP)

> Am 19.01.2018 um 14:47 schrieb Konstantin Ryabitsev > : > > On 2018-01-19 03:37 AM, Jani Nikula wrote: >> On a side note, I was browsing for the generated kernel documentation at >> https://www.kernel.org/ and realized that AFAICT there are no links to >>

Re: [PATCH v2] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

On Fri, Jan 19, 2018 at 5:53 PM, Marc Zyngier wrote: > On 18/01/18 05:28, Ganapatrao Kulkarni wrote: >> This erratum is observed on the ThunderX2 GICv3 ITS. When a >> MOVI command is used to change affinity of a LPI to a collection/cpu >> on another node, the LPI is not

Re: kernel.org documentation link (was Re: Protecting code integrity with PGP)

On Fri, 19 Jan 2018, Konstantin Ryabitsev wrote: > On 2018-01-19 03:37 AM, Jani Nikula wrote: >> On a side note, I was browsing for the generated kernel documentation at >> https://www.kernel.org/ and realized that AFAICT there are no links to >>

kernel.org documentation link (was Re: Protecting code integrity with PGP)

On 2018-01-19 03:37 AM, Jani Nikula wrote: > On a side note, I was browsing for the generated kernel documentation at > https://www.kernel.org/ and realized that AFAICT there are no links to > https://www.kernel.org/doc/ or https://www.kernel.org/doc/html/latest/. > > The former could use some

[PATCH v2] Documentation: rapidio: move sysfs interface to ABI

Right now, the description of the rapidio sysfs interfaces is in Documentation/rapidio/sysfs.txt. Since these are a part of the ABI, they should be in Documentation/ABI along with the rest. Signed-off-by: Aishwarya Pant --- Movement of sysfs interface is not absolutely

Re: [PATCH v2] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

On 18/01/18 05:28, Ganapatrao Kulkarni wrote: > This erratum is observed on the ThunderX2 GICv3 ITS. When a > MOVI command is used to change affinity of a LPI to a collection/cpu > on another node, the LPI is not delivered to the cpu. > An additional INV command is required after the MOVI to

[PATCH v4 1/1] runchecks: Generalize make C={1,2} to support multiple checkers

Add scripts/runchecks which has generic support for running checker tools in a convenient and user friendly way that the author hopes can contribute to rein in issues detected by these tools in a manageable and convenient way. scripts/runchecks provides the following basic functionality: * Makes

[PATCH v4 0/1] Support for generalized use of make C={1,2} via a wrapper program

This patch implements features to make it easier to run checkers on the entire kernel as part of automatic and developer testing. This is done by replacing the sparse specific setup for the C={1,2} variable in the makefiles with setup for running scripts/runchecks, a new program that can run any

Re: [PATCH 3/3] encrypted-keys: document new fscrypt key format

Thank you Ted, On Wed, 2018-01-17 at 13:05 -0500, Theodore Ts'o wrote: > On Wed, Jan 17, 2018 at 02:38:59PM +, André Draszik wrote: > > > > [...] > > > > > > Please be very clear about exactly what security properties are > > > achieved > > > by > > > using encrypted-keys. > > > > I've left

Re: [PATCH net-next v3] xfrm: Add ESN support for IPSec HW offload

On Mon, Jan 15, 2018 at 10:06:06AM -0800, Shannon Nelson wrote: > On 1/14/2018 1:39 AM, yoss...@mellanox.com wrote: > > From: Yossef Efraim > > > > This patch adds ESN support to IPsec device offload. > > Adding new xfrm device operation to synchronize device ESN. > > > >

Re: Protecting code integrity with PGP (kernel developer version)

On Thu, 18 Jan 2018, Randy Dunlap wrote: > On 01/18/2018 06:09 AM, Jani Nikula wrote: >> On Thu, 11 Jan 2018, Konstantin Ryabitsev >> wrote: >>> On Wed, Jan 10, 2018 at 02:05:16PM -0700, Jonathan Corbet wrote: > Does such document