Re: LICENSES: Missing ISC text & possibly a category ("Not recommended" vs. "Preferred licenses")

On Sun, Apr 29, 2018 at 07:26:17AM +0200, Greg Kroah-Hartman wrote: > I see it is only used in a very small number of dts files. Why not just > use BSD-2-Clause instead? What do you find in ISC that is not available > to you with just BSD? ISC license is a simplified version of the BSD license

Re: LICENSES: Missing ISC text & possibly a category ("Not recommended" vs. "Preferred licenses")

On Sat, Apr 28, 2018 at 11:25:17PM +0200, Rafał Miłecki wrote: > Hi, > > Due to some maintainers *preferring* BSD-compatible license for DTS > files [0], I was writing mine using ISC. I had no very special reason > for it: I was choosing between BSD-2-Clause, MIT and ISC. I've chosen > ISC as I

LICENSES: Missing ISC text & possibly a category ("Not recommended" vs. "Preferred licenses")

Hi, Due to some maintainers *preferring* BSD-compatible license for DTS files [0], I was writing mine using ISC. I had no very special reason for it: I was choosing between BSD-2-Clause, MIT and ISC. I've chosen ISC as I read about its "removal of language deemed unnecessary". I took a moment to

[PATCH] kselftests: fix grammar and non-ASCII space

From: Randy Dunlap This is a small cleanup to kselftest.rst: - Fix some language typos in the usage instructions. - Change one non-ASCII space to an ASCII space. Signed-off-by: Randy Dunlap --- Documentation/dev-tools/kselftest.rst | 12

Re: [PATCH] documentation: core-api: rearrange a few kernel-api chapters and sections

On 04/27/2018 04:17 PM, Jonathan Corbet wrote: > On Thu, 26 Apr 2018 18:11:02 -0700 > Randy Dunlap wrote: > >> Rearrange some kernel-api chapters and sections to group them >> together better. >> >> - move Bit Operations from Basic C Library Functions to Basic >> Kernel

Re: [net-next v2] ipv6: sr: Add documentation for seg_flowlabel sysctl

From: Ahmed Abdelsalam Date: Fri, 27 Apr 2018 17:51:48 +0200 > This patch adds a documentation for seg_flowlabel sysctl into > Documentation/networking/ip-sysctl.txt > > Signed-off-by: Ahmed Abdelsalam Applied, thank you. -- To unsubscribe from this

Re: [PATCH 2/4] fpga: manager: change api, don't use drvdata

On 04/27/2018 04:30 PM, Alan Tull wrote: > On Fri, Apr 27, 2018 at 1:26 PM, Florian Fainelli > wrote: >> On 04/26/2018 06:26 PM, Moritz Fischer wrote: >>> From: Alan Tull >>> >>> Change fpga_mgr_register to not set or use drvdata. This supports >>> the

Re: [PATCH 0/7] docs/vm: update KSM documentation

On Tue, 24 Apr 2018 09:40:21 +0300 Mike Rapoport wrote: > These patches extend KSM documentation with high level design overview and > some details about reverse mappings and split the userspace interface > description to Documentation/admin-guide/mm. > > The

Re: [PATCH] Documentation: driver-api: fix device_connection.rst kernel-doc error

On Thu, 26 Apr 2018 18:29:41 -0700 Randy Dunlap wrote: > Using incorrect :functions: syntax (extra space) causes an odd kernel-doc > warning, so fix that. > > Documentation/driver-api/device_connection.rst:42: ERROR: Error in > "kernel-doc" directive: Applied, thanks.

Re: [PATCH] documentation: core-api: rearrange a few kernel-api chapters and sections

On Thu, 26 Apr 2018 18:11:02 -0700 Randy Dunlap wrote: > Rearrange some kernel-api chapters and sections to group them > together better. > > - move Bit Operations from Basic C Library Functions to Basic > Kernel Library Functions (now adjacent to Bitmap Operations

Re: [PATCH 0/7] docs/vm: start moving files do Documentation/admin-guide`

On Wed, 18 Apr 2018 11:07:43 +0300 Mike Rapoport wrote: > These pacthes begin categorizing memory management documentation. The > documents that describe userspace APIs and do not overload the reader with > implementation details can be moved to

Re: [PATCH v2 0/3] coresight: Refresh documenation

On Tue, 17 Apr 2018 10:08:04 -0600 Mathieu Poirier wrote: > Now that the perf tools CoreSight support is upstream this set adds > documentation to go with it and move things around so that topics > are located together. I've applied the set, thanks. jon -- To

Re: [PATCH v2] doc: dev-tools: kselftest.rst: update contributing new tests

On Thu, 19 Apr 2018 12:28:25 +0200 Anders Roxell wrote: > Add a description that the kernel headers should be used as far as it is > possible and then the system headers. > > Signed-off-by: Anders Roxell Applied, thanks. jon -- To

Re: [PATCH v3] docs: kernel-parameters.txt: Fix whitespace

On Wed, 18 Apr 2018 20:51:39 +0200 Thymo van Beers wrote: > Some lines used spaces instead of tabs at line start. > This can cause mangled lines in editors due to inconsistency. > > Replace spaces for tabs where appropriate. Applied, thanks. jon -- To unsubscribe from

Re: [PATCH] linux-next: ftrace/docs: Fix spelling typos in ftrace-users.rst

On Fri, 27 Apr 2018 18:17:09 -0400 Steven Rostedt wrote: > I just noticed that this was never applied. > > Jon, can you take this? Wow...from November. Not sure what happened...applied now, thanks. jon -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH] linux-next: ftrace/docs: Fix spelling typos in ftrace-users.rst

I just noticed that this was never applied. Jon, can you take this? -- Steve On Mon, 27 Nov 2017 22:46:36 -0500 Steven Rostedt wrote: > On Tue, 28 Nov 2017 12:26:13 +0900 > Masanari Iida wrote: > > > This patch corrects some spelling typo in

[PATCH v6 3/8] sysctl: Warn when a clamped sysctl parameter is set out of range

Even with clamped sysctl parameters, it is still not that straight forward to figure out the exact range of those parameters. One may try to write extreme parameter values to see if they get clamped. To make it easier, a warning with the expected range will now be printed into the kernel ring

[PATCH v6 2/8] proc/sysctl: Provide additional ctl_table.flags checks

Checking code is added to provide the following additional ctl_table.flags checks: 1) No unknown flag is allowed. 2) Minimum of a range cannot be larger than the maximum value. 3) The signed and unsigned flags are mutually exclusive. 4) The proc_handler should be consistent with the signed or

[PATCH v6 4/8] ipc: Clamp msgmni and shmmni to the real IPCMNI limit

A user can write arbitrary integer values to msgmni and shmmni sysctl parameters without getting error, but the actual limit is really IPCMNI (32k). This can mislead users as they think they can get a value that is not real. Enforcing the limit by failing the sysctl parameter write, however, can

[PATCH v6 1/8] sysctl: Add flags to support min/max range clamping

When minimum/maximum values are specified for a sysctl parameter in the ctl_table structure with proc_dointvec_minmax() handler, update to that parameter will fail with error if the given value is outside of the required range. There are use cases where it may be better to clamp the value of the

[PATCH v6 6/8] test_sysctl: Add range clamping test

Add a range clamping test to verify that the input value will be clamped if it exceeds the builtin maximum or minimum value. Below is the expected test run result: Running test: sysctl_test_0006 - run #0 Checking range minimum clamping ... ok Checking range maximum clamping ... ok Checking range

[PATCH v6 5/8] ipc: Clamp semmni to the real IPCMNI limit

For SysV semaphores, the semmni value is the last part of the 4-element sem number array. To make semmni behave in a similar way to msgmni and shmmni, we can't directly use the _minmax handler. Instead, a special sem specific handler is added to check the last argument to make sure that it is

[PATCH v6 7/8] ipc: Allow boot time extension of IPCMNI from 32k to 2M

The maximum number of unique System V IPC identifiers was limited to 32k. That limit should be big enough for most use cases. However, there are some users out there requesting for more. To satisfy the need of those users, a new boot time kernel option "ipcmni_extend" is added to extend the

[PATCH v6 8/8] ipc: Conserve sequence numbers in extended IPCMNI mode

The mixing in of a sequence number into the IPC IDs is probably to avoid ID reuse in userspace as much as possible. With extended IPCMNI mode, the number of usable sequence numbers is greatly reduced leading to higher chance of ID reuse. To address this issue, we need to conserve the sequence

[PATCH v6 0/8] ipc: Clamp *mni to the real IPCMNI limit & increase that limit

v5->v6: - Consolidate the 3 ctl_table flags into 2. - Make similar changes to proc_doulongvec_minmax() and its associates to complete the clamping change. - Remove the sysctl registration failure test patch for now for later consideration. - Add extra braces to patch 1 to reduce code

[PATCH 0/3] Better integrate seccomp logging and auditing

Seccomp received improved logging controls in v4.14. Applications can opt into logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading filters. They can also debug filter matching with the new SECCOMP_RET_LOG action.

[PATCH 1/3] seccomp: Separate read and write code for actions_logged sysctl

Break the read and write paths of the kernel.seccomp.actions_logged sysctl into separate functions to maintain readability. An upcoming change will need to audit writes, but not reads, of this sysctl which would introduce too many conditional code paths on whether or not the 'write' parameter

[PATCH 2/3] seccomp: Audit attempts to modify the actions_logged sysctl

The decision to log a seccomp action will always be subject to the value of the kernel.seccomp.actions_logged sysctl, even for processes that are being inspected via the audit subsystem, in an upcoming patch. Therefore, we need to emit an audit record on attempts at writing to the actions_logged

[PATCH 3/3] seccomp: Don't special case audited processes when logging

Seccomp logging for "handled" actions such as RET_TRAP, RET_TRACE, or RET_ERRNO can be very noisy for processes that are being audited. This patch modifies the seccomp logging behavior to treat processes that are being inspected via the audit subsystem the same as processes that aren't under

Re: [PATCH 2/4] fpga: manager: change api, don't use drvdata

On 04/26/2018 06:26 PM, Moritz Fischer wrote: > From: Alan Tull > > Change fpga_mgr_register to not set or use drvdata. This supports > the case where a PCIe device has more than one manager. > > Add fpga_mgr_create/free functions. Change fpga_mgr_register and >

[PATCH 00/10] Add MSI-X support on pcitest tool

Depends of the following serie [1]. Add MSI-X support on pcitest tool. Add new callbacks methods and handlers to trigger the MSI-X interrupts on the EP DesignWare IP driver. Allow to set/get MSI-X EP maximum capability number. Rework on set/get and triggering MSI methods on EP DesignWare IP

[PATCH 08/10] PCI: endpoint: functions/pci-epf-test: Replace lower into upper case characters

Replace all initial lower case character into upper case in comments and debug printks. Signed-off-by: Gustavo Pimentel --- drivers/pci/endpoint/functions/pci-epf-test.c | 26 +- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git

[PATCH 05/10] PCI: dwc: Add legacy interrupt callback handler

Add a legacy interrupt callback handler. Currently DesignWare IP don't allow triggering the legacy interrupt. Signed-off-by: Gustavo Pimentel --- drivers/pci/dwc/pcie-designware-ep.c | 10 ++ drivers/pci/dwc/pcie-designware-plat.c | 3 +--

[PATCH 07/10] misc: pci_endpoint_test: Replace lower into upper case characters

Replace all initial lower case character into upper case in comments and debug printks. Signed-off-by: Gustavo Pimentel --- drivers/misc/pci_endpoint_test.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git

[PATCH 10/10] misc: pci_endpoint_test: Use pci_irq_vector function

Replace "pdev->irq + index" operation by the pci_irq_vector() call, that converts from device vector to Linux IRQ. (suggestion made by Alan Douglas). Signed-off-by: Gustavo Pimentel --- drivers/misc/pci_endpoint_test.c | 10 +- 1 file changed, 5

[PATCH 04/10] PCI: dwc: Rework MSI callbacks handler

Remove duplicate defines located on pcie-designware.h file already available on /include/uapi/linux/pci-regs.h file. Add pci_epc_set_msi() maximum 32 interrupts validation. Signed-off-by: Gustavo Pimentel --- drivers/pci/dwc/pcie-designware-ep.c | 49

[PATCH 06/10] misc: pci_endpoint_test: Add MSI-X support

Add MSI-X support and update driver documentation accordingly. Add new driver parameter to allow interruption type selection. Modify the Legacy/MSI/MSI-X test process, by: - Add and use a specific register located in a BAR, which defines the interrupt type is been triggered. - Move the

[PATCH 09/10] tools: PCI: Add MSI-X support

Add MSI-X support to pcitest tool. Modify pcitest.sh script to accomodate MSI-X interrupt tests. Signed-off-by: Gustavo Pimentel --- include/uapi/linux/pcitest.h | 1 + tools/pci/pcitest.c | 18 +- tools/pci/pcitest.sh | 25

[PATCH 01/10] PCI: endpoint: Add MSI-X interfaces

Add PCI_EPC_IRQ_MSIX type. Add MSI-X callbacks signatures to ops structure. Add sysfs interface for set/get MSI-X capability maximum number. Signed-off-by: Gustavo Pimentel --- drivers/pci/endpoint/pci-ep-cfs.c | 24

[PATCH 02/10] PCI: dwc: Add MSI-X callbacks handler

Change pcie_raise_irq() signature, namely the interrupt_num variable type from u8 to u16 to accommodate the 2048 maximum MSI-X interrupts. Add PCIe config space capability search function. Add sysfs set/get interface to allow to change of EP MSI-X maximum number. Add EP MSI-X callback for

[PATCH 03/10] PCI: cadence: Update cdns_pcie_ep_raise_irq function signature

Change cdns_pcie_ep_raise_irq() signature, namely the interrupt_num variable type from u8 to u16 to accommodate the 2048 maximum MSI-X interrupts. Signed-off-by: Gustavo Pimentel Acked-by: Alan Douglas ---

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

On Fri, 27 Apr 2018 17:09:14 +0100 Will Deacon wrote: > Kim, > > [Ganapat: please don't let this discussion disrupt your PMU driver > development. You can safely ignore it for now :)] > > On Fri, Apr 27, 2018 at 10:46:29AM -0500, Kim Phillips wrote: > > On Fri, 27 Apr

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

Kim, [Ganapat: please don't let this discussion disrupt your PMU driver development. You can safely ignore it for now :)] On Fri, Apr 27, 2018 at 10:46:29AM -0500, Kim Phillips wrote: > On Fri, 27 Apr 2018 15:37:20 +0100 > Will Deacon wrote: > > > On Fri, Apr 27, 2018 at

Re: [net-next] ipv6: sr: Add documentation for seg_flowlabel sysctl

On Fri, 27 Apr 2018 08:47:14 -0700 Randy Dunlap wrote: > On 04/27/2018 03:35 AM, Ahmed Abdelsalam wrote: > > This patch adds a documentation for seg_flowlabel sysctl into > > Documentation/networking/ip-sysctl.txt > > > > Signed-off-by: Ahmed Abdelsalam

[net-next v2] ipv6: sr: Add documentation for seg_flowlabel sysctl

This patch adds a documentation for seg_flowlabel sysctl into Documentation/networking/ip-sysctl.txt Signed-off-by: Ahmed Abdelsalam --- Documentation/networking/ip-sysctl.txt | 13 + 1 file changed, 13 insertions(+) diff --git

Re: [net-next] ipv6: sr: Add documentation for seg_flowlabel sysctl

On 04/27/2018 03:35 AM, Ahmed Abdelsalam wrote: > This patch adds a documentation for seg_flowlabel sysctl into > Documentation/networking/ip-sysctl.txt > > Signed-off-by: Ahmed Abdelsalam > --- > Documentation/networking/ip-sysctl.txt | 13 + > 1 file changed,

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

On Fri, 27 Apr 2018 15:37:20 +0100 Will Deacon wrote: > On Fri, Apr 27, 2018 at 08:15:25AM -0500, Kim Phillips wrote: > > On Fri, 27 Apr 2018 10:30:27 +0100 > > Mark Rutland wrote: > > > On Thu, Apr 26, 2018 at 05:06:24PM -0500, Kim Phillips wrote: > >

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

On Fri, Apr 27, 2018 at 08:15:25AM -0500, Kim Phillips wrote: > On Fri, 27 Apr 2018 10:30:27 +0100 > Mark Rutland wrote: > > On Thu, Apr 26, 2018 at 05:06:24PM -0500, Kim Phillips wrote: > > > On Wed, 25 Apr 2018 14:30:47 +0530 > > > Ganapatrao Kulkarni

Re: [RFC tip/locking/lockdep v6 01/20] lockdep/Documention: Recursive read lock detection reasoning

(Copy more people) On Wed, Apr 11, 2018 at 09:50:51PM +0800, Boqun Feng wrote: > This patch add the documentation piece for the reasoning of deadlock > detection related to recursive read lock. The following sections are > added: > > * Explain what is a recursive read lock, and what deadlock

Re: [PATCH] documentation: core-api: rearrange a few kernel-api chapters and sections

On Thu, Apr 26, 2018 at 06:11:02PM -0700, Randy Dunlap wrote: > Rearrange some kernel-api chapters and sections to group them > together better. > > - move Bit Operations from Basic C Library Functions to Basic > Kernel Library Functions (now adjacent to Bitmap Operations since > they are not

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

On Fri, 27 Apr 2018 10:30:27 +0100 Mark Rutland wrote: > Hi Kim, > > On Thu, Apr 26, 2018 at 05:06:24PM -0500, Kim Phillips wrote: > > On Wed, 25 Apr 2018 14:30:47 +0530 > > Ganapatrao Kulkarni wrote: > > > > > +static int

Re: [PATCH] Documentation: driver-api: fix device_connection.rst kernel-doc error

On Thu, Apr 26, 2018 at 06:29:41PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Using incorrect :functions: syntax (extra space) causes an odd kernel-doc > warning, so fix that. > > Documentation/driver-api/device_connection.rst:42: ERROR: Error in > "kernel-doc"

Re: [PATCH v3 11/15] ARM: dts: dra7-evm: Add wilink8 wlan support

Hi Rob, On Wednesday 25 April 2018 08:17 PM, Rob Herring wrote: > On Wed, Apr 25, 2018 at 7:54 AM, Kishon Vijay Abraham I wrote: >> From: Hari Nagalla >> >> The wilink module is a combo wireless connectivity sdio >> card based on Texas Instrument's wl18xx

Re: [PATCH v3 04/15] ARM: dts: dra74x-mmc-iodelay: Add a new pinctrl group for clk line without pullup

Hi Tony, On Wednesday 25 April 2018 07:05 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I [180425 12:57]: >> --- a/arch/arm/boot/dts/dra74x-mmc-iodelay.dtsi >> +++ b/arch/arm/boot/dts/dra74x-mmc-iodelay.dtsi >> @@ -49,6 +49,17 @@ >> >; >> }; >> >> +

[net-next] ipv6: sr: Add documentation for seg_flowlabel sysctl

This patch adds a documentation for seg_flowlabel sysctl into Documentation/networking/ip-sysctl.txt Signed-off-by: Ahmed Abdelsalam --- Documentation/networking/ip-sysctl.txt | 13 + 1 file changed, 13 insertions(+) diff --git

Re: [PATCH bpf-next v2] bpf, doc: Update bpf_jit_enable limitation for CONFIG_BPF_JIT_ALWAYS_ON

On 04/27/2018 12:02 PM, Leo Yan wrote: > When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for > bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2 > for JIT opcode dumping; this patch is to update the doc for it. > > Suggested-by: Daniel Borkmann

[PATCH bpf-next v2] bpf, doc: Update bpf_jit_enable limitation for CONFIG_BPF_JIT_ALWAYS_ON

When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2 for JIT opcode dumping; this patch is to update the doc for it. Suggested-by: Daniel Borkmann Signed-off-by: Leo Yan

Re: [PATCH bpf-next] bpf, doc: Update bpf_jit_enable limitation for CONFIG_BPF_JIT_ALWAYS_ON

On 04/27/2018 11:49 AM, Leo Yan wrote: > On Fri, Apr 27, 2018 at 11:44:44AM +0200, Daniel Borkmann wrote: >> On 04/26/2018 04:26 AM, Leo Yan wrote: >>> When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for >>> bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2 >>> for

Re: [PATCH bpf-next] bpf, doc: Update bpf_jit_enable limitation for CONFIG_BPF_JIT_ALWAYS_ON

On Fri, Apr 27, 2018 at 11:44:44AM +0200, Daniel Borkmann wrote: > On 04/26/2018 04:26 AM, Leo Yan wrote: > > When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for > > bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2 > > for JIT opcode dumping; this patch is to

Re: [PATCH bpf-next] bpf, doc: Update bpf_jit_enable limitation for CONFIG_BPF_JIT_ALWAYS_ON

On 04/26/2018 04:26 AM, Leo Yan wrote: > When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for > bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2 > for JIT opcode dumping; this patch is to update the doc for it. > > Signed-off-by: Leo Yan > ---

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

Hi Kim, On Thu, Apr 26, 2018 at 05:06:24PM -0500, Kim Phillips wrote: > On Wed, 25 Apr 2018 14:30:47 +0530 > Ganapatrao Kulkarni wrote: > > > +static int thunderx2_uncore_event_init(struct perf_event *event) > This PMU driver can be made more user-friendly by

Re: [PATCH bpf-next v4 00/10] bpf: document eBPF helpers and add a script to generate man page

On 04/25/2018 07:16 PM, Quentin Monnet wrote: > eBPF helper functions can be called from within eBPF programs to perform > a variety of tasks that would be otherwise hard or impossible to do with > eBPF itself. There is a growing number of such helper functions in the > kernel, but documentation

Re: [PATCH v4 1/2] perf: uncore: Adding documentation for ThunderX2 pmu uncore driver

On Fri, Apr 27, 2018 at 2:25 AM, Randy Dunlap wrote: > Hi, > > Just a few typo corrections... > > On 04/25/2018 02:00 AM, Ganapatrao Kulkarni wrote: >> Documentation for the UNCORE PMUs on Cavium's ThunderX2 SoC. >> The SoC has PMU support in its L3 cache controller (L3C)

[PATCH] Documentation: driver-api: fix device_connection.rst kernel-doc error

From: Randy Dunlap Using incorrect :functions: syntax (extra space) causes an odd kernel-doc warning, so fix that. Documentation/driver-api/device_connection.rst:42: ERROR: Error in "kernel-doc" directive: Signed-off-by: Randy Dunlap Cc: Heikki

[PATCH 3/4] fpga: bridge: change api, don't use drvdata

From: Alan Tull Change fpga_bridge_register to not set drvdata. This is to support the case where a PCIe device can have more than one bridge. Add API functions to create/free the fpga bridge struct. Change fpga_bridge_register/unregister to take FPGA bridge struct as the

[PATCH 1/4] fpga: region: don't use drvdata in common fpga code

From: Alan Tull Changes to fpga_region_register function to not set drvdata. Setting drvdata is fine for DT based devices that will have one region per platform device. However PCIe based devices may have multiple FPGA regions under one PCIe device. Without these changes,

[PATCH 4/4] fpga: region: change api, add fpga_region_create/free

From: Alan Tull Add fpga_region_create/free API functions. Change fpga_region_register to take FPGA region struct as the only parameter. Change fpga_region_unregister to return void. struct fpga_region *fpga_region_create(struct device *dev, struct

[PATCH 2/4] fpga: manager: change api, don't use drvdata

From: Alan Tull Change fpga_mgr_register to not set or use drvdata. This supports the case where a PCIe device has more than one manager. Add fpga_mgr_create/free functions. Change fpga_mgr_register and fpga_mgr_unregister functions to take the mgr struct as their only

[PATCH 0/4] FPGA Manager Patches for 4.18

Hi Greg, Here's Alan's reworked patchset changing the API for creating and registering FPGA Managers, Bridges and Regions following your suggestions on the API. These go on top of Paolo and Alan's patches that you queued up the other day. Thanks, Moritz Alan Tull (4): fpga: region: don't

[PATCH] documentation: core-api: rearrange a few kernel-api chapters and sections

From: Randy Dunlap Rearrange some kernel-api chapters and sections to group them together better. - move Bit Operations from Basic C Library Functions to Basic Kernel Library Functions (now adjacent to Bitmap Operations since they are not typical C library functions)

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

On Wed, 25 Apr 2018 14:30:47 +0530 Ganapatrao Kulkarni wrote: > +static int thunderx2_uncore_event_init(struct perf_event *event) ... > + /* > + * SOC PMU counters are shared across all cores. > + * Therefore, it does not support per-process mode. >

[RESEND PATCH v3] docs: kernel-parameters.txt: Fix whitespace

Some lines used spaces instead of tabs at line start. This can cause mangled lines in editors due to inconsistency. Replace spaces for tabs where appropriate. Signed-off-by: Thymo van Beers Reviewed-by: Randy Dunlap --- Changes in v3: - Change

Re: [PATCH v4 1/2] perf: uncore: Adding documentation for ThunderX2 pmu uncore driver

Hi, Just a few typo corrections... On 04/25/2018 02:00 AM, Ganapatrao Kulkarni wrote: > Documentation for the UNCORE PMUs on Cavium's ThunderX2 SoC. > The SoC has PMU support in its L3 cache controller (L3C) and in the > DDR4 Memory Controller (DMC). > > Signed-off-by: Ganapatrao Kulkarni

Re: [PATCH 0/6] arm64: untag user pointers passed to the kernel

On Wed, Apr 25, 2018 at 04:45:37PM +0200, Andrey Konovalov wrote: > On Thu, Apr 19, 2018 at 11:33 AM, Kirill A. Shutemov > wrote: > > On Wed, Apr 18, 2018 at 08:53:09PM +0200, Andrey Konovalov wrote: > >> arm64 has a feature called Top Byte Ignore, which allows to embed

Re: [PATCH 4/6] mm, arm64: untag user addresses in mm/gup.c

On Wed, Apr 18, 2018 at 08:53:13PM +0200, Andrey Konovalov wrote: > diff --git a/mm/gup.c b/mm/gup.c > index 76af4cfeaf68..fb375de7d40d 100644 > --- a/mm/gup.c > +++ b/mm/gup.c > @@ -386,6 +386,8 @@ struct page *follow_page_mask(struct vm_area_struct *vma, > struct page *page; > struct

Re: [PATCH v2] gpiolib: add hogs support for machine code

2018-04-26 14:07 GMT+02:00 Linus Walleij : > On Tue, Apr 10, 2018 at 10:30 PM, Bartosz Golaszewski wrote: > >> Board files constitute a significant part of the users of the legacy >> GPIO framework. In many cases they only export a line and set its >>

Re: [PATCH 3/6] arm64: untag user addresses in copy_from_user and others

On Wed, Apr 18, 2018 at 08:53:12PM +0200, Andrey Konovalov wrote: > @@ -238,12 +239,15 @@ static inline void uaccess_enable_not_uao(void) > /* > * Sanitise a uaccess pointer such that it becomes NULL if above the > * current addr_limit. > + * Also untag user pointers that have the top byte

Re: [RFC 06/10] misc: pci_endpoint_test: Add MSI-X support

Hi Kishon, On 24/04/2018 12:43, Kishon Vijay Abraham I wrote: > Hi, > > On Tuesday 24 April 2018 04:27 PM, Gustavo Pimentel wrote: >> Hi Kishon, >> >> On 24/04/2018 08:19, Kishon Vijay Abraham I wrote: >>> Hi, >>> >>> On Tuesday 17 April 2018 11:08 PM, Gustavo Pimentel wrote: Hi Kishon,

Re: [RFC 01/10] PCI: dwc: Add MSI-X callbacks handler

Hi Kishon, On 24/04/2018 12:24, Kishon Vijay Abraham I wrote: > Hi, > > On Tuesday 24 April 2018 03:06 PM, Gustavo Pimentel wrote: >> Hi Kishon, >> >> On 24/04/2018 08:07, Kishon Vijay Abraham I wrote: >>> Hi, >>> >>> On Monday 23 April 2018 03:06 PM, Gustavo Pimentel wrote: Hi Kishon,

Re: [PATCH v2] gpiolib: add hogs support for machine code

On Thu, Apr 12, 2018 at 10:00 PM, Christian Lamparter wrote: > The problem is that unlike native gpio-controllers, pinctrls need > to have a "pin/gpio range" defined before any gpio-hogs can be added. Indeed. But the primary use case (correct me if I am wrong Bartosz) is to

Re: [PATCH v2] gpiolib: add hogs support for machine code

On Tue, Apr 10, 2018 at 10:30 PM, Bartosz Golaszewski wrote: > Board files constitute a significant part of the users of the legacy > GPIO framework. In many cases they only export a line and set its > desired value. We could use GPIO hogs for that like we do for DT and > ACPI but

Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver

Hi, On Wed, Apr 25, 2018 at 02:30:47PM +0530, Ganapatrao Kulkarni wrote: > + > +/* L3c and DMC has 16 and 8 channels per socket respectively. > + * Each Channel supports UNCORE PMU device and consists of > + * 4 independent programmable counters. Counters are 32 bit > + * and does not support

Re: [PATCH v2 3/7] powerpc: use task_pid_nr() for TID allocation

On 25/04/18 07:12, Sukadev Bhattiprolu wrote: Yes. Like with PIDR, was trying to assign TIDR initially to all threads. But since only a subset of threads need/use TIDR, we can assign the value later (when set_thread_tidr() is called). So we should be able to use task_pid_nr() then. OK.

Re: [PATCH v4 09/10] gpio: Add a driver for Cadence I3C GPIO expander

On Fri, Mar 30, 2018 at 9:47 AM, Boris Brezillon wrote: > Add a driver for Cadence I3C GPIO expander. > > Signed-off-by: Boris Brezillon This is pretty much OK, and I don't want to raise the bar even higher for you to get this code into

[PATCH bpf-next] bpf, doc: Update bpf_jit_enable limitation for CONFIG_BPF_JIT_ALWAYS_ON

When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2 for JIT opcode dumping; this patch is to update the doc for it. Signed-off-by: Leo Yan --- Documentation/networking/filter.txt | 6 ++ 1

[PATCH v2 1/1] misc: IBM Virtual Management Channel Driver (VMC)

This driver is a logical device which provides an interface between the hypervisor and a management partition. This interface is like a message passing interface. This management partition is intended to provide an alternative to HMC-based system management. VMC enables the Management LPAR to

[PATCH v2 0/1] misc: IBM Virtual Management Channel Driver (VMC)

Steven Royer had previously attempted to upstream this driver two years ago, but never got the chance to address the concerns from Greg Kroah-Hartman. The thread with the initial upstream is: https://lkml.org/lkml/2016/2/16/918 I have addressed the following: Version 1: - Documentation - Use of

[PATCH bpf-next v4 03/10] bpf: add documentation for eBPF helpers (12-22)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 02/10] bpf: add documentation for eBPF helpers (01-11)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 10/10] bpf: update bpf.h uapi header for tools

Update tools/include/uapi/linux/bpf.h file in order to reflect the changes for BPF helper functions documentation introduced in previous commits. Signed-off-by: Quentin Monnet --- tools/include/uapi/linux/bpf.h | 1776 +++- 1

[PATCH bpf-next v4 09/10] bpf: add documentation for eBPF helpers (65-66)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 08/10] bpf: add documentation for eBPF helpers (58-64)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 05/10] bpf: add documentation for eBPF helpers (33-41)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 07/10] bpf: add documentation for eBPF helpers (51-57)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 06/10] bpf: add documentation for eBPF helpers (42-50)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 01/10] bpf: add script and prepare bpf.h for new helpers documentation

Remove previous "overview" of eBPF helpers from user bpf.h header. Replace it by a comment explaining how to process the new documentation (to come in following patches) with a Python script to produce RST, then man page documentation. Also add the aforementioned Python script under scripts/. It

[PATCH bpf-next v4 04/10] bpf: add documentation for eBPF helpers (23-32)

Add documentation for eBPF helper functions to bpf.h user header file. This documentation can be parsed with the Python script provided in another commit of the patch series, in order to provide a RST document that can later be converted into a man page. The objective is to make the documentation

[PATCH bpf-next v4 00/10] bpf: document eBPF helpers and add a script to generate man page

eBPF helper functions can be called from within eBPF programs to perform a variety of tasks that would be otherwise hard or impossible to do with eBPF itself. There is a growing number of such helper functions in the kernel, but documentation is scarce. The main user space header file does contain

Re: [PATCH v5 0/2] perf: riscv: Preliminary Perf Event Support on RISC-V

On Tue, 24 Apr 2018 20:19:36 PDT (-0700), alan...@andestech.com wrote: Hi Atish, Palmer, On Tue, Apr 24, 2018 at 06:15:49PM -0700, Atish Patra wrote: On 4/24/18 5:29 PM, Palmer Dabbelt wrote: >On Tue, 24 Apr 2018 15:16:16 PDT (-0700), atish.pa...@wdc.com wrote: >>On 4/24/18 12:44 PM, Palmer

Re: [PATCH v5 0/2] perf: riscv: Preliminary Perf Event Support on RISC-V

On Tue, 24 Apr 2018 18:15:49 PDT (-0700), atish.pa...@wdc.com wrote: On 4/24/18 5:29 PM, Palmer Dabbelt wrote: On Tue, 24 Apr 2018 15:16:16 PDT (-0700), atish.pa...@wdc.com wrote: On 4/24/18 12:44 PM, Palmer Dabbelt wrote: On Tue, 24 Apr 2018 12:27:26 PDT (-0700), atish.pa...@wdc.com wrote:

<    5   6   7   8   9   10   11   12   13   14   >