Re: [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 01/13/2017 01:26 PM, Stefano Stabellini wrote: > On Fri, 13 Jan 2017, Boris Ostrovsky wrote: >> On 01/12/2017 04:39 PM, Stefano Stabellini wrote: >>> The following commit: >>> >>> commit 72a9b186292d98494f26cfd24a1621796209 >>> Author: KarimAllah Ahmed >>> Date: Fri

Re: [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 01/13/2017 01:26 PM, Stefano Stabellini wrote: > On Fri, 13 Jan 2017, Boris Ostrovsky wrote: >> On 01/12/2017 04:39 PM, Stefano Stabellini wrote: >>> The following commit: >>> >>> commit 72a9b186292d98494f26cfd24a1621796209 >>> Author: KarimAllah Ahmed >>> Date: Fri Aug 26 23:55:36 2016

Re: [RFC PATCH v2 10/10] dt-bindings: Document devicetree binding for ARM SPE

On Fri, Jan 13, 2017 at 04:03:49PM +, Will Deacon wrote: > This patch documents the devicetree binding in use for ARM SPE. > > Cc: Mark Rutland > Cc: Rob Herring > Signed-off-by: Will Deacon > --- >

Re: [RFC PATCH v2 10/10] dt-bindings: Document devicetree binding for ARM SPE

On Fri, Jan 13, 2017 at 04:03:49PM +, Will Deacon wrote: > This patch documents the devicetree binding in use for ARM SPE. > > Cc: Mark Rutland > Cc: Rob Herring > Signed-off-by: Will Deacon > --- > Documentation/devicetree/bindings/arm/spe-pmu.txt | 20 > 1 file

Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...

On 13/01/17 17:37, David Daney wrote: > On 01/13/2017 08:15 AM, Marc Zyngier wrote: >> Thanks Linus for looping me in. >> >> On 12/01/17 22:35, David Daney wrote: >>> Hi Thomas, >>> >>> I am trying to figure out how to handle this situation: >>> >>>handle_level_irq() >>>

Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...

On 13/01/17 17:37, David Daney wrote: > On 01/13/2017 08:15 AM, Marc Zyngier wrote: >> Thanks Linus for looping me in. >> >> On 12/01/17 22:35, David Daney wrote: >>> Hi Thomas, >>> >>> I am trying to figure out how to handle this situation: >>> >>>handle_level_irq() >>>

Re: [PATCH] platform/x86: Add IMS/ZII SCU driver

On Fri, Jan 13, 2017 at 06:38:28PM +0200, Andy Shevchenko wrote: > On Wed, Jan 11, 2017 at 11:26 PM, Florian Fainelli > wrote: > > From: Guenter Roeck > > > > This patch adds support for the IMS (now Zodiac Inflight Innovations) > > SCU Generation 1/2/3

Re: [PATCH] platform/x86: Add IMS/ZII SCU driver

On Fri, Jan 13, 2017 at 06:38:28PM +0200, Andy Shevchenko wrote: > On Wed, Jan 11, 2017 at 11:26 PM, Florian Fainelli > wrote: > > From: Guenter Roeck > > > > This patch adds support for the IMS (now Zodiac Inflight Innovations) > > SCU Generation 1/2/3 platform driver. This driver registers

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Fri, 13 Jan 2017, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote: > > On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini > > wrote: > >> On Wed, 11 Jan 2017, Dan Streetman wrote: > >>> On Tue, Jan 10, 2017 at 8:25 PM,

Re: [Xen-devel] [PATCH] xen: do not re-use pirq number cached in pci device msi msg data

On Fri, 13 Jan 2017, Dan Streetman wrote: > On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote: > > On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini > > wrote: > >> On Wed, 11 Jan 2017, Dan Streetman wrote: > >>> On Tue, Jan 10, 2017 at 8:25 PM, Stefano Stabellini > >>> wrote: > >>> > On

Re: [PATCH] flow disector: check if arp_eth is null rather than arp

On Fri, 2017-01-13 at 18:25 +, Colin Ian King wrote: > On 13/01/17 18:24, Eric Dumazet wrote: > > It looks that we try very hard to add critical bugs in flow dissector. > > > > This is embarrassing really. > > > > I am questioning if the __skb_header_pointer() is correct > > > > Why using

Re: [PATCH] flow disector: check if arp_eth is null rather than arp

On Fri, 2017-01-13 at 18:25 +, Colin Ian King wrote: > On 13/01/17 18:24, Eric Dumazet wrote: > > It looks that we try very hard to add critical bugs in flow dissector. > > > > This is embarrassing really. > > > > I am questioning if the __skb_header_pointer() is correct > > > > Why using

Re: [PATCH] flow disector: check if arp_eth is null rather than arp

On Fri, 2017-01-13 at 13:34 +, Colin King wrote: > From: Colin Ian King > > arp is being checked instead of arp_eth to see if the call to > __skb_header_pointer failed. Fix this by checking arp_eth is > null instead of arp. > > CoverityScan CID#1396428 ("Logically

Re: [PATCH] flow disector: check if arp_eth is null rather than arp

On Fri, 2017-01-13 at 13:34 +, Colin King wrote: > From: Colin Ian King > > arp is being checked instead of arp_eth to see if the call to > __skb_header_pointer failed. Fix this by checking arp_eth is > null instead of arp. > > CoverityScan CID#1396428 ("Logically dead code") on 2nd > arp

[PATCH] misc: mic: constify virtio_config_ops structures

Declare virtio_config_ops structure as const as it is only stored in the config field of a virtio_device structure. This field is of type const, so virtio_config_ops structures having this property can be declared const. Done using Coccinelle: @r1 disable optional_qualifier@ identifier i;

[PATCH] misc: mic: constify virtio_config_ops structures

Declare virtio_config_ops structure as const as it is only stored in the config field of a virtio_device structure. This field is of type const, so virtio_config_ops structures having this property can be declared const. Done using Coccinelle: @r1 disable optional_qualifier@ identifier i;

RE: [PATCH v2 00/26] IB: Optimize DMA mapping

Hi Bart, This series applied to 4.10-rc3 breaks hfi1 sdma engines. [ 34.712343] hfi1 :82:00.0: hfi1_0: SDMA (0) engine error: 0x21 state s50_HwHaltWait [ 34.722752] hfi1 :82:00.0: hfi1_0: SDMA (0) descq_head: 0 descq_tail: 3 freecnt: 2044 FLE 0 [ 34.733933] hfi1 :82:00.0:

RE: [PATCH v2 00/26] IB: Optimize DMA mapping

Hi Bart, This series applied to 4.10-rc3 breaks hfi1 sdma engines. [ 34.712343] hfi1 :82:00.0: hfi1_0: SDMA (0) engine error: 0x21 state s50_HwHaltWait [ 34.722752] hfi1 :82:00.0: hfi1_0: SDMA (0) descq_head: 0 descq_tail: 3 freecnt: 2044 FLE 0 [ 34.733933] hfi1 :82:00.0:

Re: [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On Fri, 13 Jan 2017, Boris Ostrovsky wrote: > On 01/12/2017 04:39 PM, Stefano Stabellini wrote: > > The following commit: > > > > commit 72a9b186292d98494f26cfd24a1621796209 > > Author: KarimAllah Ahmed > > Date: Fri Aug 26 23:55:36 2016 +0200 > > > > xen: Remove

Re: [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On Fri, 13 Jan 2017, Boris Ostrovsky wrote: > On 01/12/2017 04:39 PM, Stefano Stabellini wrote: > > The following commit: > > > > commit 72a9b186292d98494f26cfd24a1621796209 > > Author: KarimAllah Ahmed > > Date: Fri Aug 26 23:55:36 2016 +0200 > > > > xen: Remove event channel

Re: [PATCH] flow disector: check if arp_eth is null rather than arp

On 13/01/17 18:24, Eric Dumazet wrote: > On Fri, 2017-01-13 at 13:34 +, Colin King wrote: >> From: Colin Ian King >> >> arp is being checked instead of arp_eth to see if the call to >> __skb_header_pointer failed. Fix this by checking arp_eth is >> null instead of

Re: [PATCH] flow disector: check if arp_eth is null rather than arp

On 13/01/17 18:24, Eric Dumazet wrote: > On Fri, 2017-01-13 at 13:34 +, Colin King wrote: >> From: Colin Ian King >> >> arp is being checked instead of arp_eth to see if the call to >> __skb_header_pointer failed. Fix this by checking arp_eth is >> null instead of arp. >> >> CoverityScan

[PATCH] perf script: Also allow forcing reading of non-root owned files by root

In 2059fc7a5a9e6677, perf report was added the option of forcing reading of non-root owned symbol file. This add the same behavior for perf script. Reported-by: Mark Drayton Signed-off-by: Yannick Brosseau --- tools/perf/builtin-script.c | 3 ++- 1 file changed,

[PATCH] perf script: Also allow forcing reading of non-root owned files by root

In 2059fc7a5a9e6677, perf report was added the option of forcing reading of non-root owned symbol file. This add the same behavior for perf script. Reported-by: Mark Drayton Signed-off-by: Yannick Brosseau --- tools/perf/builtin-script.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[GIT PULL] arm64 fixes for 4.10-rc4

Hi Linus, Please pull the arm64 fixes below. Thanks. The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes

[GIT PULL] arm64 fixes for 4.10-rc4

Hi Linus, Please pull the arm64 fixes below. Thanks. The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes

Re: [PATCH v3] ARM: dts: Add LEGO MINDSTORMS EV3 dts

On 01/13/2017 12:16 PM, David Lechner wrote: On 01/13/2017 06:04 AM, Sekhar Nori wrote: On Friday 13 January 2017 02:02 AM, David Lechner wrote: This adds a device tree definition file for LEGO MINDSTORMS EV3. ... There are couple of checkpatch errors that show up. The compatible

Re: [PATCH v3] ARM: dts: Add LEGO MINDSTORMS EV3 dts

On 01/13/2017 12:16 PM, David Lechner wrote: On 01/13/2017 06:04 AM, Sekhar Nori wrote: On Friday 13 January 2017 02:02 AM, David Lechner wrote: This adds a device tree definition file for LEGO MINDSTORMS EV3. ... There are couple of checkpatch errors that show up. The compatible

Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support

* Vignesh R [170113 00:03]: > This patch series re enables DMA support for UART 8250_omap driver. > > Tested on AM335x, AM437x that use EDMA and OMAP5 and DRA74 EVM with > SDMA. Is 8250_omap serial console working for you on omap5 in general? I've noticed that it's really

Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support

* Vignesh R [170113 00:03]: > This patch series re enables DMA support for UART 8250_omap driver. > > Tested on AM335x, AM437x that use EDMA and OMAP5 and DRA74 EVM with > SDMA. Is 8250_omap serial console working for you on omap5 in general? I've noticed that it's really unresponsive for me

Re: [RFC PATCH v2 09/10] drivers/perf: Add support for ARMv8.2 Statistical Profiling Extension

On Fri, 13 Jan 2017 17:03:07 + Will Deacon wrote: > On Fri, Jan 13, 2017 at 10:40:42AM -0600, Kim Phillips wrote: > > On Fri, 13 Jan 2017 16:03:48 + > > Will Deacon wrote: > > > > > +#define DRVNAME "arm_spe_pmu" > > >

Re: [RFC PATCH v2 09/10] drivers/perf: Add support for ARMv8.2 Statistical Profiling Extension

On Fri, 13 Jan 2017 17:03:07 + Will Deacon wrote: > On Fri, Jan 13, 2017 at 10:40:42AM -0600, Kim Phillips wrote: > > On Fri, 13 Jan 2017 16:03:48 + > > Will Deacon wrote: > > > > > +#define DRVNAME "arm_spe_pmu" > > > > PMU is implied. "arm_spe"? > > As

Re: [PATCH v3] ARM: dts: Add LEGO MINDSTORMS EV3 dts

On 01/13/2017 06:04 AM, Sekhar Nori wrote: On Friday 13 January 2017 02:02 AM, David Lechner wrote: This adds a device tree definition file for LEGO MINDSTORMS EV3. ... There are couple of checkpatch errors that show up. The compatible "lego,ev3" needs to be documented in

Re: [PATCH v3] ARM: dts: Add LEGO MINDSTORMS EV3 dts

On 01/13/2017 06:04 AM, Sekhar Nori wrote: On Friday 13 January 2017 02:02 AM, David Lechner wrote: This adds a device tree definition file for LEGO MINDSTORMS EV3. ... There are couple of checkpatch errors that show up. The compatible "lego,ev3" needs to be documented in

Re: [PATCH 17/17] spi/topcliff-pch: One check less in pch_spi_set_tx()

Hi Markus, On Fri, Jan 13, 2017 at 6:28 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 13 Jan 2017 17:30:46 +0100 > > Delete a duplicate check after a bit of exception handling was moved into > a previous if branch

Re: [PATCH 17/17] spi/topcliff-pch: One check less in pch_spi_set_tx()

Hi Markus, On Fri, Jan 13, 2017 at 6:28 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 13 Jan 2017 17:30:46 +0100 > > Delete a duplicate check after a bit of exception handling was moved into > a previous if branch of this function. This is not equivalent: if

Re: [tpmdd-devel] [PATCH RFC v2 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Fri, 2017-01-13 at 11:01 -0700, Jason Gunthorpe wrote: > On Fri, Jan 13, 2017 at 09:40:08AM -0800, James Bottomley wrote: > > On Fri, 2017-01-13 at 10:25 -0700, Jason Gunthorpe wrote: > > > On Thu, Jan 12, 2017 at 10:56:28PM +0200, Jarkko Sakkinen wrote: > > > > > > > > dev_t tpm_devt; > > >

Re: [tpmdd-devel] [PATCH RFC v2 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Fri, 2017-01-13 at 11:01 -0700, Jason Gunthorpe wrote: > On Fri, Jan 13, 2017 at 09:40:08AM -0800, James Bottomley wrote: > > On Fri, 2017-01-13 at 10:25 -0700, Jason Gunthorpe wrote: > > > On Thu, Jan 12, 2017 at 10:56:28PM +0200, Jarkko Sakkinen wrote: > > > > > > > > dev_t tpm_devt; > > >

Re: [tpmdd-devel] [PATCH v8 2/2] tpm: add securityfs support for TPM 2.0 firmware event log

On 01/11/2017 02:54 AM, Nayna Jain wrote: Unlike the device driver support for TPM 1.2, the TPM 2.0 does not support the securityfs pseudo files for displaying the firmware event log. This patch enables support for providing the TPM 2.0 event log in binary form. TPM 2.0 event log supports a

Re: [tpmdd-devel] [PATCH v8 2/2] tpm: add securityfs support for TPM 2.0 firmware event log

On 01/11/2017 02:54 AM, Nayna Jain wrote: Unlike the device driver support for TPM 1.2, the TPM 2.0 does not support the securityfs pseudo files for displaying the firmware event log. This patch enables support for providing the TPM 2.0 event log in binary form. TPM 2.0 event log supports a

Re: [PATCH 16/37] PCI: endpoint: Introduce configfs entry for configuring EP functions

Hi Kishon, a couple comments on the configfs layout based on my experiments with your previous drop to implement a NVMe device using it. I don't think most of these configfs files should be present here, as they are properties of the implemented PCIe devices. E.g. for my NVMe device they will

Re: [PATCH 16/37] PCI: endpoint: Introduce configfs entry for configuring EP functions

Hi Kishon, a couple comments on the configfs layout based on my experiments with your previous drop to implement a NVMe device using it. I don't think most of these configfs files should be present here, as they are properties of the implemented PCIe devices. E.g. for my NVMe device they will

Re: [patch 2/3] KVM: x86: add KVM_HC_CLOCK_OFFSET hypercall

On Fri, Jan 13, 2017 at 06:07:40PM +0100, Radim Krcmar wrote: > 2017-01-13 13:43-0200, Marcelo Tosatti: > > On Fri, Jan 13, 2017 at 04:31:58PM +0100, Radim Krcmar wrote: > >> 2017-01-13 10:01-0200, Marcelo Tosatti: > >> > Add a hypercall to retrieve the host realtime clock > >> > and the TSC value

Re: [patch 2/3] KVM: x86: add KVM_HC_CLOCK_OFFSET hypercall

On Fri, Jan 13, 2017 at 06:07:40PM +0100, Radim Krcmar wrote: > 2017-01-13 13:43-0200, Marcelo Tosatti: > > On Fri, Jan 13, 2017 at 04:31:58PM +0100, Radim Krcmar wrote: > >> 2017-01-13 10:01-0200, Marcelo Tosatti: > >> > Add a hypercall to retrieve the host realtime clock > >> > and the TSC value

Re: [patch 1/3] KVM: x86: provide realtime host clock via vsyscall notifiers

On Fri, Jan 13, 2017 at 05:28:09PM +0100, Radim Krcmar wrote: > 2017-01-13 13:34-0200, Marcelo Tosatti: > > On Fri, Jan 13, 2017 at 04:18:04PM +0100, Radim Krcmar wrote: > >> 2017-01-13 10:01-0200, Marcelo Tosatti: > >> > Expose the realtime host clock and save the TSC value > >> > used for the

Re: [patch 3/3] PTP: add kvm PTP driver

On Fri, Jan 13, 2017 at 04:56:58PM +0100, Radim Krcmar wrote: > 2017-01-13 10:01-0200, Marcelo Tosatti: > > Add a driver with gettime method returning hosts realtime clock. > > This allows Chrony to synchronize host and guest clocks with > > high precision (see results below). > > > > chronyc>

Re: [patch 3/3] PTP: add kvm PTP driver

On Fri, Jan 13, 2017 at 04:56:58PM +0100, Radim Krcmar wrote: > 2017-01-13 10:01-0200, Marcelo Tosatti: > > Add a driver with gettime method returning hosts realtime clock. > > This allows Chrony to synchronize host and guest clocks with > > high precision (see results below). > > > > chronyc>

Re: [patch 1/3] KVM: x86: provide realtime host clock via vsyscall notifiers

On Fri, Jan 13, 2017 at 05:28:09PM +0100, Radim Krcmar wrote: > 2017-01-13 13:34-0200, Marcelo Tosatti: > > On Fri, Jan 13, 2017 at 04:18:04PM +0100, Radim Krcmar wrote: > >> 2017-01-13 10:01-0200, Marcelo Tosatti: > >> > Expose the realtime host clock and save the TSC value > >> > used for the

Re: [PATCH] Documentation: cpuset: Fix 'cpuset.tasks' -> 'tasks'

On Fri, 13 Jan 2017 09:44:34 -0800 "W. Trevor King" wrote: > > So I'll confess that I don't understand this change. All of the > > control files are referred to as cpuset.whatever in this document; > > why should this one, in particular, be different? > > 'tasks' is part of

Re: [PATCH] Documentation: cpuset: Fix 'cpuset.tasks' -> 'tasks'

On Fri, 13 Jan 2017 09:44:34 -0800 "W. Trevor King" wrote: > > So I'll confess that I don't understand this change. All of the > > control files are referred to as cpuset.whatever in this document; > > why should this one, in particular, be different? > > 'tasks' is part of the generic

[PATCH] net: constify mdiobb_ops structures

Declare mdiobb_ops structures as const as they are only stored in the ops field of mdiobb_ctrl structures. This field is of type const, so mdiobb_ops structures having this property can be declared const too. Done using Coccinelle: @r disable optional_qualifier@ identifier x; position p; @@

[PATCH] net: constify mdiobb_ops structures

Declare mdiobb_ops structures as const as they are only stored in the ops field of mdiobb_ctrl structures. This field is of type const, so mdiobb_ops structures having this property can be declared const too. Done using Coccinelle: @r disable optional_qualifier@ identifier x; position p; @@

Re: [PATCH V2 0/6] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip

On 01/12/2017 10:20 PM, Keerthy wrote: The Davinci GPIO driver is implemented to work with one monolithic Davinci GPIO platform device which may have up to Y(144) gpios. The Davinci GPIO driver instantiates number of GPIO chips with max 32 gpio pins per each during initialization and one IRQ

Re: [PATCH V2 0/6] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip

On 01/12/2017 10:20 PM, Keerthy wrote: The Davinci GPIO driver is implemented to work with one monolithic Davinci GPIO platform device which may have up to Y(144) gpios. The Davinci GPIO driver instantiates number of GPIO chips with max 32 gpio pins per each during initialization and one IRQ

Re: [tpmdd-devel] [PATCH RFC v2 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Fri, Jan 13, 2017 at 09:40:08AM -0800, James Bottomley wrote: > On Fri, 2017-01-13 at 10:25 -0700, Jason Gunthorpe wrote: > > On Thu, Jan 12, 2017 at 10:56:28PM +0200, Jarkko Sakkinen wrote: > > > > > > dev_t tpm_devt; > > > > > > But they should have different major device numbers. > > > >

Re: [tpmdd-devel] [PATCH RFC v2 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Fri, Jan 13, 2017 at 09:40:08AM -0800, James Bottomley wrote: > On Fri, 2017-01-13 at 10:25 -0700, Jason Gunthorpe wrote: > > On Thu, Jan 12, 2017 at 10:56:28PM +0200, Jarkko Sakkinen wrote: > > > > > > dev_t tpm_devt; > > > > > > But they should have different major device numbers. > > > >

[PATCH] KVM: VMX: downgrade warning on unexpected exit code

2017-01-02 11:23+0100, Dmitry Vyukov: > Hello, > > I've got the following warning while running syzkaller fuzzer: > > WARNING: CPU: 2 PID: 13257 at arch/x86/kvm/vmx.c:8633 > vmx_handle_exit+0x262b/0x38b0 arch/x86/kvm/vmx.c:8633 > vmx: unexpected exit reason 0xb > CPU: 2 PID: 13257 Comm:

[PATCH] KVM: VMX: downgrade warning on unexpected exit code

2017-01-02 11:23+0100, Dmitry Vyukov: > Hello, > > I've got the following warning while running syzkaller fuzzer: > > WARNING: CPU: 2 PID: 13257 at arch/x86/kvm/vmx.c:8633 > vmx_handle_exit+0x262b/0x38b0 arch/x86/kvm/vmx.c:8633 > vmx: unexpected exit reason 0xb > CPU: 2 PID: 13257 Comm:

[PATCH v4 0/2] reset: Make optional functions really optional.

v4: - Change the way error handling was being processed when in optional mode. v3: - Improve description of changes ocurring in the patchset - Add 2 new return errors. v2: - Make some comments more explicit - Add optional flag to reduce code duplication - Change shared flag from int to

[PATCH v4 1/2] reset: Change shared flag from int to bool

Since the new parameter being added is going to be a bool this patch changes the shared flag from int to bool to match the new parameter. Signed-off-by: Ramiro Oliveira --- drivers/reset/core.c | 8 include/linux/reset.h | 32

[PATCH v4 0/2] reset: Make optional functions really optional.

v4: - Change the way error handling was being processed when in optional mode. v3: - Improve description of changes ocurring in the patchset - Add 2 new return errors. v2: - Make some comments more explicit - Add optional flag to reduce code duplication - Change shared flag from int to

[PATCH v4 1/2] reset: Change shared flag from int to bool

Since the new parameter being added is going to be a bool this patch changes the shared flag from int to bool to match the new parameter. Signed-off-by: Ramiro Oliveira --- drivers/reset/core.c | 8 include/linux/reset.h | 32 2 files changed, 20

[PATCH v4 2/2] reset: make optional functions really optional

The *_get_optional_* functions weren't really optional so this patch makes them really optional. These *_get_optional_* functions will now return NULL instead of an error if no matching reset phandle is found in the DT, and all the reset_control_* functions now accept NULL rstc pointers.

[PATCH v4 2/2] reset: make optional functions really optional

The *_get_optional_* functions weren't really optional so this patch makes them really optional. These *_get_optional_* functions will now return NULL instead of an error if no matching reset phandle is found in the DT, and all the reset_control_* functions now accept NULL rstc pointers.

Re: kvm: WARNING in x86_emulate_insn

2017-01-12 14:55+0100, Dmitry Vyukov: > Hello, > > I've got the following WARNING in x86_emulate_insn while running > syzkaller fuzzer: > > WARNING: CPU: 2 PID: 18646 at arch/x86/kvm/emulate.c:5558 > x86_emulate_insn+0x16a5/0x4090 arch/x86/kvm/emulate.c:5572 > Modules linked in: > CPU: 2 PID:

Re: kvm: WARNING in x86_emulate_insn

2017-01-12 14:55+0100, Dmitry Vyukov: > Hello, > > I've got the following WARNING in x86_emulate_insn while running > syzkaller fuzzer: > > WARNING: CPU: 2 PID: 18646 at arch/x86/kvm/emulate.c:5558 > x86_emulate_insn+0x16a5/0x4090 arch/x86/kvm/emulate.c:5572 > Modules linked in: > CPU: 2 PID:

Re: [PATCH 12/37] PCI: dwc: Create a new config symbol to enable pci dwc host

Hi Kishon, Às 10:26 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: > Now that pci designware host has a separate file, create a new > config symbol to select the host only driver. This is in preparation > to enable endpoint support to designware driver. > > Signed-off-by: Kishon Vijay Abraham

Re: [PATCH 12/37] PCI: dwc: Create a new config symbol to enable pci dwc host

Hi Kishon, Às 10:26 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: > Now that pci designware host has a separate file, create a new > config symbol to select the host only driver. This is in preparation > to enable endpoint support to designware driver. > > Signed-off-by: Kishon Vijay Abraham

Re: [PATCH 3/6 linux-next] fs/affs: make affs exportable

On Wed, Jan 04, 2017 at 06:53:31AM +0100, Fabian Frederick wrote: > > > > On 03 January 2017 at 23:29 Al Viro wrote: > > > > > > On Tue, Jan 03, 2017 at 10:30:39PM +0100, Fabian Frederick wrote: > > > Add standard functions making AFFS work with NFS. > > > > > >

Re: [PATCH 3/6 linux-next] fs/affs: make affs exportable

On Wed, Jan 04, 2017 at 06:53:31AM +0100, Fabian Frederick wrote: > > > > On 03 January 2017 at 23:29 Al Viro wrote: > > > > > > On Tue, Jan 03, 2017 at 10:30:39PM +0100, Fabian Frederick wrote: > > > Add standard functions making AFFS work with NFS. > > > > > > Functions based on ext4

Re: [PATCH] Documentation: cpuset: Fix 'cpuset.tasks' -> 'tasks'

On Fri, Jan 13, 2017 at 10:27:42AM -0700, Jonathan Corbet wrote: > > -if a task's pid is written to another cpusets 'cpuset.tasks' file, then its > > +if a task's pid is written to another cpuset's 'tasks' file, then its > > So I'll confess that I don't understand this change. All of the >

Re: [PATCH] Documentation: cpuset: Fix 'cpuset.tasks' -> 'tasks'

On Fri, Jan 13, 2017 at 10:27:42AM -0700, Jonathan Corbet wrote: > > -if a task's pid is written to another cpusets 'cpuset.tasks' file, then its > > +if a task's pid is written to another cpuset's 'tasks' file, then its > > So I'll confess that I don't understand this change. All of the >

Re: [PATCH 08/10] blk-mq-sched: add framework for MQ capable IO schedulers

On 01/13/2017 05:41 PM, Omar Sandoval wrote: > On Fri, Jan 13, 2017 at 12:15:17PM +0100, Hannes Reinecke wrote: >> On 01/11/2017 10:40 PM, Jens Axboe wrote: >>> This adds a set of hooks that intercepts the blk-mq path of >>> allocating/inserting/issuing/completing requests, allowing >>> us to

Re: [PATCH 08/10] blk-mq-sched: add framework for MQ capable IO schedulers

On 01/13/2017 05:41 PM, Omar Sandoval wrote: > On Fri, Jan 13, 2017 at 12:15:17PM +0100, Hannes Reinecke wrote: >> On 01/11/2017 10:40 PM, Jens Axboe wrote: >>> This adds a set of hooks that intercepts the blk-mq path of >>> allocating/inserting/issuing/completing requests, allowing >>> us to

Re: [tpmdd-devel] [PATCH RFC v2 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Fri, 2017-01-13 at 10:25 -0700, Jason Gunthorpe wrote: > On Thu, Jan 12, 2017 at 10:56:28PM +0200, Jarkko Sakkinen wrote: > > > > dev_t tpm_devt; > > > > But they should have different major device numbers. > > major/minors don't really matter these days since they are dynamic Right,

Re: [tpmdd-devel] [PATCH RFC v2 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Fri, 2017-01-13 at 10:25 -0700, Jason Gunthorpe wrote: > On Thu, Jan 12, 2017 at 10:56:28PM +0200, Jarkko Sakkinen wrote: > > > > dev_t tpm_devt; > > > > But they should have different major device numbers. > > major/minors don't really matter these days since they are dynamic Right,

[GIT PULL] Ceph fixes for 4.10-rc4

Hi Linus, The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) are available in the git repository at: https://github.com/ceph/ceph-client.git tags/ceph-for-4.10-rc4 for you to fetch changes up to

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/13/2017 09:08 AM, Dave Hansen wrote: On 01/13/2017 07:29 AM, Rob Gardner wrote: so perhaps ADI should simply be disallowed for memory mapped to files, and this particular complication can be avoided. Thoughts? What's a "file" from your perspective? In Linux, shared memory is a file.

[GIT PULL] Ceph fixes for 4.10-rc4

Hi Linus, The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) are available in the git repository at: https://github.com/ceph/ceph-client.git tags/ceph-for-4.10-rc4 for you to fetch changes up to

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/13/2017 09:08 AM, Dave Hansen wrote: On 01/13/2017 07:29 AM, Rob Gardner wrote: so perhaps ADI should simply be disallowed for memory mapped to files, and this particular complication can be avoided. Thoughts? What's a "file" from your perspective? In Linux, shared memory is a file.

Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...

On 01/13/2017 08:15 AM, Marc Zyngier wrote: Thanks Linus for looping me in. On 12/01/17 22:35, David Daney wrote: Hi Thomas, I am trying to figure out how to handle this situation: handle_level_irq() +---+ handle_fasteoi_irq()

Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...

On 01/13/2017 08:15 AM, Marc Zyngier wrote: Thanks Linus for looping me in. On 12/01/17 22:35, David Daney wrote: Hi Thomas, I am trying to figure out how to handle this situation: handle_level_irq() +---+ handle_fasteoi_irq()

Re: [PATCH v11 01/12] dt-bindings: display: mediatek: update supported chips

On Wed, Jan 11, 2017 at 02:51:02PM +0800, YT Shen wrote: > Add decriptions about supported chips, including MT2701 & MT8173 > > Signed-off-by: YT Shen > --- > Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 ++ >

Re: [PATCH v11 01/12] dt-bindings: display: mediatek: update supported chips

On Wed, Jan 11, 2017 at 02:51:02PM +0800, YT Shen wrote: > Add decriptions about supported chips, including MT2701 & MT8173 > > Signed-off-by: YT Shen > --- > Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 ++ >

Re: [PATCH v1 2/2] arm: dts: mt2701: add nor flash node

On 01/13/2017 05:56 PM, Boris Brezillon wrote: > On Fri, 13 Jan 2017 17:44:12 +0100 > Marek Vasut wrote: > >> On 01/13/2017 05:28 PM, Boris Brezillon wrote: >>> On Fri, 13 Jan 2017 17:13:55 +0100 >>> Marek Vasut wrote: >>> On 01/13/2017

Re: [PATCH] Documentation: Update CPU hotplug and move it to core-api

On Thu, 22 Dec 2016 17:19:34 +0100 Sebastian Andrzej Siewior wrote: > The current CPU hotplug is outdated. During the update to what we > currently have I rewrote it partly and moved to sphinx format. OK, I've applied this (finally) to the docs tree, even though I do kind

Re: [PATCH v1 2/2] arm: dts: mt2701: add nor flash node

On 01/13/2017 05:56 PM, Boris Brezillon wrote: > On Fri, 13 Jan 2017 17:44:12 +0100 > Marek Vasut wrote: > >> On 01/13/2017 05:28 PM, Boris Brezillon wrote: >>> On Fri, 13 Jan 2017 17:13:55 +0100 >>> Marek Vasut wrote: >>> On 01/13/2017 04:12 PM, Matthias Brugger wrote: > >

Re: [PATCH] Documentation: Update CPU hotplug and move it to core-api

On Thu, 22 Dec 2016 17:19:34 +0100 Sebastian Andrzej Siewior wrote: > The current CPU hotplug is outdated. During the update to what we > currently have I rewrote it partly and moved to sphinx format. OK, I've applied this (finally) to the docs tree, even though I do kind of agree with Jani

Re: [PATCH v2] tcp: fix tcp_fastopen unaligned access complaints on sparc

From: Shannon Nelson Date: Thu, 12 Jan 2017 14:24:58 -0800 > Fix up a data alignment issue on sparc by swapping the order > of the cookie byte array field with the length field in > struct tcp_fastopen_cookie, and making it a proper union > to clean up the typecasting.

Re: [PATCH v2] tcp: fix tcp_fastopen unaligned access complaints on sparc

From: Shannon Nelson Date: Thu, 12 Jan 2017 14:24:58 -0800 > Fix up a data alignment issue on sparc by swapping the order > of the cookie byte array field with the length field in > struct tcp_fastopen_cookie, and making it a proper union > to clean up the typecasting. > > This addresses log

Re: [PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

On Wed, Jan 11, 2017 at 03:33:57PM +0900, Hoegeun Kwon wrote: > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang > Signed-off-by: Hoegeun Kwon

Re: [PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

On Wed, Jan 11, 2017 at 03:33:57PM +0900, Hoegeun Kwon wrote: > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang > Signed-off-by: Hoegeun Kwon > Tested-by: Chanwoo Choi > Reviewed-by:

[RFC PATCH v3 1/2] tracing: add TRACE_EVENT_MAP_COND

This new macro allows to hook conditional tracepoint probes to pre-existing trace events. This allows to create specialized versions of the same tracepoint without having to explicitly call every possible tracepoints in the instrumented code. In order to use it, a TRACE_EVENT must already exist,

[RFC PATCH v3 0/2] Extend scheduling tracepoints

This patchset proposes a way to extend the existing scheduling tracepoints. The intent is to allow to output relevant priority informations based on the scheduling class of the tasks without breaking the existing tracepoints or having to handle the various cases in the scheduler code. The

[RFC PATCH v3 2/2] tracing: add policy-based sched_switch events

Add 3 new tracepoints: sched_switch_fair, sched_switch_rt and sched_switch_dl. These conditional tracepoints are emitted based on the scheduling class of the next task. Each of these tracepoint gets rid of the prio field from the original sched_switch and replaces it with fields that are relevant

[RFC PATCH v3 1/2] tracing: add TRACE_EVENT_MAP_COND

This new macro allows to hook conditional tracepoint probes to pre-existing trace events. This allows to create specialized versions of the same tracepoint without having to explicitly call every possible tracepoints in the instrumented code. In order to use it, a TRACE_EVENT must already exist,

[RFC PATCH v3 0/2] Extend scheduling tracepoints

This patchset proposes a way to extend the existing scheduling tracepoints. The intent is to allow to output relevant priority informations based on the scheduling class of the tasks without breaking the existing tracepoints or having to handle the various cases in the scheduler code. The

[RFC PATCH v3 2/2] tracing: add policy-based sched_switch events

Add 3 new tracepoints: sched_switch_fair, sched_switch_rt and sched_switch_dl. These conditional tracepoints are emitted based on the scheduling class of the next task. Each of these tracepoint gets rid of the prio field from the original sched_switch and replaces it with fields that are relevant

[PATCH 17/17] spi/topcliff-pch: One check less in pch_spi_set_tx()

From: Markus Elfring Date: Fri, 13 Jan 2017 17:30:46 +0100 Delete a duplicate check after a bit of exception handling was moved into a previous if branch of this function. Signed-off-by: Markus Elfring ---

[PATCH 17/17] spi/topcliff-pch: One check less in pch_spi_set_tx()

From: Markus Elfring Date: Fri, 13 Jan 2017 17:30:46 +0100 Delete a duplicate check after a bit of exception handling was moved into a previous if branch of this function. Signed-off-by: Markus Elfring --- drivers/spi/spi-topcliff-pch.c | 25 ++--- 1 file changed, 14

<    1   2   3   4   5   6   7   8   9   10   >