Re: [PATCH] mfd: arizona: Add missing disable of PM runtime on probe error path

On Mon, 27 Jun 2016, Charles Keepax wrote: > Signed-off-by: Charles Keepax > --- > drivers/mfd/arizona-core.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) Applied, thanks. > diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c

Re: [PATCH v6 5/5] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64

Hi Daniel, On 27/06/16 15:33, Daniel Lezcano wrote: On 06/14/2016 04:48 PM, Sudeep Holla wrote: Now that ACPI processor idle driver supports LPI(Low Power Idle), lets enable ACPI_PROCESSOR_IDLE for ARM64 too. This patch just removes the IA64 and X86 dependency on ACPI_PROCESSOR_IDLE Cc:

Re: [PATCH] mfd: arizona: Add missing disable of PM runtime on probe error path

On Mon, 27 Jun 2016, Charles Keepax wrote: > Signed-off-by: Charles Keepax > --- > drivers/mfd/arizona-core.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) Applied, thanks. > diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c > index bf27179..e4f97b3 100644 >

Re: [PATCH v6 5/5] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64

Hi Daniel, On 27/06/16 15:33, Daniel Lezcano wrote: On 06/14/2016 04:48 PM, Sudeep Holla wrote: Now that ACPI processor idle driver supports LPI(Low Power Idle), lets enable ACPI_PROCESSOR_IDLE for ARM64 too. This patch just removes the IA64 and X86 dependency on ACPI_PROCESSOR_IDLE Cc:

Re: [PATCH v4 15/29] x86/mm/64: Enable vmapped stacks

On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote: > This allows x86_64 kernels to enable vmapped stacks. There are a > couple of interesting bits. > > First, x86 lazily faults in top-level paging entries for the vmalloc > area. This won't work if we get a page fault while

Re: [PATCH v4 15/29] x86/mm/64: Enable vmapped stacks

On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote: > This allows x86_64 kernels to enable vmapped stacks. There are a > couple of interesting bits. > > First, x86 lazily faults in top-level paging entries for the vmalloc > area. This won't work if we get a page fault while trying to access

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

On Mon, Jun 27, 2016 at 02:53:16PM +0200, Hans de Goede wrote: > Note this does not mean that all pm_power_off implementations > are going to be happy with machine_power_off leaving irqs > enabled, I would esp. expect the efi and psci implementations > to potentially be unhappy about this. See

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

On Mon, Jun 27, 2016 at 02:53:16PM +0200, Hans de Goede wrote: > Note this does not mean that all pm_power_off implementations > are going to be happy with machine_power_off leaving irqs > enabled, I would esp. expect the efi and psci implementations > to potentially be unhappy about this. See

[RFC] [PATCH v2 1/3] scatterlist: Add support to clone scatterlist

Occasionally there are times you need to tweak a chained S/G list while maintaining the original list. This function will duplicate the passed in chained S/G list and return a pointer to the cloned copy. The function also supports passing in a length that can be equal or less than the original

[RFC] [PATCH v2 1/3] scatterlist: Add support to clone scatterlist

Occasionally there are times you need to tweak a chained S/G list while maintaining the original list. This function will duplicate the passed in chained S/G list and return a pointer to the cloned copy. The function also supports passing in a length that can be equal or less than the original

Re: [PATCH 2/3] powerpc/spinlock: support vcpu preempted check

Hi Xinhui, On Mon, Jun 27, 2016 at 01:41:29PM -0400, Pan Xinhui wrote: > This is to fix some holder preemption issues. Spinning at one > vcpu which is preempted is meaningless. > > Kernel need such interfaces, So lets support it. > > We also should suooprt both the shared and dedicated mode. >

Re: [PATCH] capabilities: add capability cgroup controller

Quoting Tejun Heo (t...@kernel.org): > Hello, Topi. > > On Sun, Jun 26, 2016 at 3:14 PM, Topi Miettinen wrote: > > The parent might be able do it if proc/pid/xyz files are still > > accessible after child exit but before its exit status is collected. But > > if the parent

Re: [PATCH 2/3] powerpc/spinlock: support vcpu preempted check

Hi Xinhui, On Mon, Jun 27, 2016 at 01:41:29PM -0400, Pan Xinhui wrote: > This is to fix some holder preemption issues. Spinning at one > vcpu which is preempted is meaningless. > > Kernel need such interfaces, So lets support it. > > We also should suooprt both the shared and dedicated mode. >

Re: [PATCH] capabilities: add capability cgroup controller

Quoting Tejun Heo (t...@kernel.org): > Hello, Topi. > > On Sun, Jun 26, 2016 at 3:14 PM, Topi Miettinen wrote: > > The parent might be able do it if proc/pid/xyz files are still > > accessible after child exit but before its exit status is collected. But > > if the parent doesn't do it (and you

[RFC] [PATCH v2 2/3] spi: omap2-mcspi: Add comments for RX only DMA buffer workaround

OMAP35x and OMAP37x mentions in the McSPI End-of-Transfer Sequences section that if the McSPI is configured as a Master and only DMA RX is being performed then the DMA transfer size needs to be reduced by 1 or 2. This was originally implemented by: commit 57c5c28dbc83 ("spi: omap2_mcspi rxdma

[RFC] [PATCH v2 2/3] spi: omap2-mcspi: Add comments for RX only DMA buffer workaround

OMAP35x and OMAP37x mentions in the McSPI End-of-Transfer Sequences section that if the McSPI is configured as a Master and only DMA RX is being performed then the DMA transfer size needs to be reduced by 1 or 2. This was originally implemented by: commit 57c5c28dbc83 ("spi: omap2_mcspi rxdma

[RFC] [PATCH v2 3/3] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping

Currently, the driver handles mapping buffers to be used by the DMA. However, there are times that the current mapping implementation will fail for certain buffers. Fortunately, the SPI framework can detect and map buffers so its usable by the DMA. Update the driver to utilize the SPI framework

[RFC] [PATCH v2 3/3] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping

Currently, the driver handles mapping buffers to be used by the DMA. However, there are times that the current mapping implementation will fail for certain buffers. Fortunately, the SPI framework can detect and map buffers so its usable by the DMA. Update the driver to utilize the SPI framework

Re: [PATCH v2 04/14] regulator: SY8106A regulator driver

On Sun, Jun 26, 2016 at 05:07:16PM +0200, Ondřej Jirman wrote: > On 26.6.2016 13:26, Mark Brown wrote: > > I'm missing almost all of this series, I've just got this and another > > patch which look like a standalone driver so it's hard to see any > > dependencies. What's going on here? > Sorry,

Re: [PATCH v2 04/14] regulator: SY8106A regulator driver

On Sun, Jun 26, 2016 at 05:07:16PM +0200, Ondřej Jirman wrote: > On 26.6.2016 13:26, Mark Brown wrote: > > I'm missing almost all of this series, I've just got this and another > > patch which look like a standalone driver so it's hard to see any > > dependencies. What's going on here? > Sorry,

Re: kthread_stop insanity (Re: [[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18)

On 06/26, Andy Lutomirski wrote: > > kthread_stop is *sick*. > > struct kthread self; > > ... > > current->vfork_done = > > ... > > do_exit(ret); > > And then some other thread goes and waits for the completion, which is > *on the stack*, which, in any sane world (e.g. with my series

Re: kthread_stop insanity (Re: [[DEBUG] force] 2642458962: BUG: unable to handle kernel paging request at ffffc90000997f18)

On 06/26, Andy Lutomirski wrote: > > kthread_stop is *sick*. > > struct kthread self; > > ... > > current->vfork_done = > > ... > > do_exit(ret); > > And then some other thread goes and waits for the completion, which is > *on the stack*, which, in any sane world (e.g. with my series

[RFC] [PATCH v2 0/3] scatterlist: Add support to clone sg_table

This patchset creates two new functions within scatterlist that allows a user to pass in a sg_table and receive a duplicate copy. The sgl in this copied table are dynamically allocated but its values such as offset, length and dma_address are the same as its variant within the sgl in the original

[RFC] [PATCH v2 0/3] scatterlist: Add support to clone sg_table

This patchset creates two new functions within scatterlist that allows a user to pass in a sg_table and receive a duplicate copy. The sgl in this copied table are dynamically allocated but its values such as offset, length and dma_address are the same as its variant within the sgl in the original

[PATCH]staging:vt6656:dpc.h:fix parantheses alignment

The following patch fixes "Alignment should match open parantheses" check thrown by checkpatch.pl Signed-off-by: Rithvik Patibandla --- drivers/staging/vt6656/dpc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/vt6656/dpc.h

[PATCH]staging:vt6656:dpc.h:fix parantheses alignment

The following patch fixes "Alignment should match open parantheses" check thrown by checkpatch.pl Signed-off-by: Rithvik Patibandla --- drivers/staging/vt6656/dpc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/vt6656/dpc.h b/drivers/staging/vt6656/dpc.h

[PATCH v2] ACPI: Execute the _PTS method when system reboot

The _PTS control method is defined in the section 7.4.1 of acpi 6.0 spec. The _PTS control method is executed by the OS during the sleep transition process for S1, S2, S3, S4, and for orderly S5 shutdown. The _PTS control method provides the BIOS a mechanism for performing some housekeeping, such

[PATCH v2] ACPI: Execute the _PTS method when system reboot

The _PTS control method is defined in the section 7.4.1 of acpi 6.0 spec. The _PTS control method is executed by the OS during the sleep transition process for S1, S2, S3, S4, and for orderly S5 shutdown. The _PTS control method provides the BIOS a mechanism for performing some housekeeping, such

[PATCH] i2c: mv64xxx: Use clk_enable_prepare and clk_disable_unprepare

Replace clk_enable and clk_prepare with clk_enable_prepare and clk_disable and clk_unprepare with clk_disable_unprepare. The Coccinelle semantic patch used to make this change is as follows: @@ expression e; @@ - clk_prepare(e); - clk_enable(e); + clk_prepare_enable(e); @@ expression e; @@ -

Re: [PATCH 2/4] ftrace/x86: Do not crash when reading wrong ftrace func

On Mon, 27 Jun 2016 15:54:35 +0200 Petr Mladek wrote: > Ftrace modifies the code on many locations. It is paranoid > and avoid a kernel crash using probe_kernel_read() and > probe_kernel_write(). The only exception is update_ftrace_func() > where where we read the old code

[PATCH] i2c: mv64xxx: Use clk_enable_prepare and clk_disable_unprepare

Replace clk_enable and clk_prepare with clk_enable_prepare and clk_disable and clk_unprepare with clk_disable_unprepare. The Coccinelle semantic patch used to make this change is as follows: @@ expression e; @@ - clk_prepare(e); - clk_enable(e); + clk_prepare_enable(e); @@ expression e; @@ -

Re: [PATCH 2/4] ftrace/x86: Do not crash when reading wrong ftrace func

On Mon, 27 Jun 2016 15:54:35 +0200 Petr Mladek wrote: > Ftrace modifies the code on many locations. It is paranoid > and avoid a kernel crash using probe_kernel_read() and > probe_kernel_write(). The only exception is update_ftrace_func() > where where we read the old code using memcpy(). > >

Re: [PATCH] dsa: mv88e6xxx: hide unused functions

From: Vivien Didelot Date: Thu, 23 Jun 2016 11:21:27 -0400 > Hi, > > Arnd Bergmann writes: > >> When CONFIG_NET_DSA_HWMON is disabled, we get warnings about two unused >> functions whose only callers are all inside of an #ifdef: >> >>

Re: [PATCH] dsa: mv88e6xxx: hide unused functions

From: Vivien Didelot Date: Thu, 23 Jun 2016 11:21:27 -0400 > Hi, > > Arnd Bergmann writes: > >> When CONFIG_NET_DSA_HWMON is disabled, we get warnings about two unused >> functions whose only callers are all inside of an #ifdef: >> >> drivers/net/dsa/mv88e6xxx.c:3257:12:

Re: [PATCH v4 3/3] acpi/pmic: Add support for PMIC regs operation region

On Mon, Jun 27, 2016 at 03:25:11PM +0200, Rafael J. Wysocki wrote: > On Mon, Jun 27, 2016 at 11:26 AM, Heikki Krogerus > wrote: > > Whoa! Hold on! > > > > On Thu, Jun 23, 2016 at 05:52:53PM -0700, Bin Gao wrote: > >> Broxton platform firmware has defined new

Re: [PATCH v4 3/3] acpi/pmic: Add support for PMIC regs operation region

On Mon, Jun 27, 2016 at 03:25:11PM +0200, Rafael J. Wysocki wrote: > On Mon, Jun 27, 2016 at 11:26 AM, Heikki Krogerus > wrote: > > Whoa! Hold on! > > > > On Thu, Jun 23, 2016 at 05:52:53PM -0700, Bin Gao wrote: > >> Broxton platform firmware has defined new customized operation regions > >>

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

Hi, On 27-06-16 15:57, Russell King - ARM Linux wrote: On Mon, Jun 27, 2016 at 02:53:16PM +0200, Hans de Goede wrote: Hi Russell, On 27-06-16 13:31, Russell King - ARM Linux wrote: I think I covered that - all the paths are indentical in the ARM architecture code, and have been identical in

Re: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu

Hi, On 27-06-16 15:57, Russell King - ARM Linux wrote: On Mon, Jun 27, 2016 at 02:53:16PM +0200, Hans de Goede wrote: Hi Russell, On 27-06-16 13:31, Russell King - ARM Linux wrote: I think I covered that - all the paths are indentical in the ARM architecture code, and have been identical in

Re: [PATCH 02/21] usb: ulpi: Support device discovery via DT

Hi, I'm fine with most of the patch, except.. On Sun, Jun 26, 2016 at 12:28:19AM -0700, Stephen Boyd wrote: > @@ -39,7 +42,10 @@ static int ulpi_match(struct device *dev, struct > device_driver *driver) > struct ulpi *ulpi = to_ulpi_dev(dev); > const struct ulpi_device_id *id; > >

Re: [PATCH 02/21] usb: ulpi: Support device discovery via DT

Hi, I'm fine with most of the patch, except.. On Sun, Jun 26, 2016 at 12:28:19AM -0700, Stephen Boyd wrote: > @@ -39,7 +42,10 @@ static int ulpi_match(struct device *dev, struct > device_driver *driver) > struct ulpi *ulpi = to_ulpi_dev(dev); > const struct ulpi_device_id *id; > >

Re: [PATCH v9 06/12] kthread: Add kthread_drain_worker()

Hi, On Fri 2016-06-24 11:54:47, Tejun Heo wrote: > On Fri, Jun 24, 2016 at 09:05:15AM +0200, Peter Zijlstra wrote: > > > Given how rare that is > > > > Could you then not remove/rework these few cases for workqueue as well > > and make that 'better' too? > > Usage of draining is rare for

Re: [PATCH v9 06/12] kthread: Add kthread_drain_worker()

Hi, On Fri 2016-06-24 11:54:47, Tejun Heo wrote: > On Fri, Jun 24, 2016 at 09:05:15AM +0200, Peter Zijlstra wrote: > > > Given how rare that is > > > > Could you then not remove/rework these few cases for workqueue as well > > and make that 'better' too? > > Usage of draining is rare for

Re: [PATCH v6 5/5] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64

On 06/14/2016 04:48 PM, Sudeep Holla wrote: Now that ACPI processor idle driver supports LPI(Low Power Idle), lets enable ACPI_PROCESSOR_IDLE for ARM64 too. This patch just removes the IA64 and X86 dependency on ACPI_PROCESSOR_IDLE Cc: linux-arm-ker...@lists.infradead.org Cc: "Rafael J.

Re: [PATCH v6 5/5] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64

On 06/14/2016 04:48 PM, Sudeep Holla wrote: Now that ACPI processor idle driver supports LPI(Low Power Idle), lets enable ACPI_PROCESSOR_IDLE for ARM64 too. This patch just removes the IA64 and X86 dependency on ACPI_PROCESSOR_IDLE Cc: linux-arm-ker...@lists.infradead.org Cc: "Rafael J.

Re: [PATCH v2 1/8] mfd: tps65218: Remove redundant read wrapper

On Monday 27 June 2016 05:53 PM, Lee Jones wrote: On Mon, 27 Jun 2016, Keerthy wrote: Currently read directly calls the repmap read function. Hence remove the redundant wrapper and use regmap read wherever needed. Signed-off-by: Keerthy --- drivers/mfd/tps65218.c

Re: [PATCH v2 1/8] mfd: tps65218: Remove redundant read wrapper

On Monday 27 June 2016 05:53 PM, Lee Jones wrote: On Mon, 27 Jun 2016, Keerthy wrote: Currently read directly calls the repmap read function. Hence remove the redundant wrapper and use regmap read wherever needed. Signed-off-by: Keerthy --- drivers/mfd/tps65218.c | 16

Re: [PATCH] net: Fix resetting network_header in neigh_resolve_output and neigh_connected_output

neigh_resolve_output and neigh_connected_output resets the skb to network_header because of the retry loop and this reset will pull down the data pointer to the network header in the first iteration then hardware header will be added, but it will overwrite any data which is inserted between

Re: [PATCH] net: Fix resetting network_header in neigh_resolve_output and neigh_connected_output

neigh_resolve_output and neigh_connected_output resets the skb to network_header because of the retry loop and this reset will pull down the data pointer to the network header in the first iteration then hardware header will be added, but it will overwrite any data which is inserted between

Re: [PATCH 5/8] KEYS: Provide software public key query function [ver #2]

Herbert Xu wrote: > > The problem is that if I'm to produce consistency with, say, the TPM > > interface, then I have to deal in wrapped/padded data - leastways as far > > as I can tell from reading the docs. > > So the TPM device is accessed through the same

Re: [PATCH 5/8] KEYS: Provide software public key query function [ver #2]

Herbert Xu wrote: > > The problem is that if I'm to produce consistency with, say, the TPM > > interface, then I have to deal in wrapped/padded data - leastways as far > > as I can tell from reading the docs. > > So the TPM device is accessed through the same interface? Where is > the code for

[PATCH] pinctrl: stm32: Modify error handling for pinctrl_register

pinctrl_register returns an ERR_PTR on error. The Coccinelle semantic patch used to make this change is as follows: @@ expression e,e1,e2; @@ e = pinctrl_register(...) ... when != e = e1 if ( - e == NULL + IS_ERR(e) ) { ... return - e2 + PTR_ERR(e) ; }

[PATCH] pinctrl: stm32: Modify error handling for pinctrl_register

pinctrl_register returns an ERR_PTR on error. The Coccinelle semantic patch used to make this change is as follows: @@ expression e,e1,e2; @@ e = pinctrl_register(...) ... when != e = e1 if ( - e == NULL + IS_ERR(e) ) { ... return - e2 + PTR_ERR(e) ; }

Re: [PATCH 3/3] locking/osq: Drop the overload of osq_lock()

On Mon, Jun 27, 2016 at 01:41:30PM -0400, Pan Xinhui wrote: > @@ -118,8 +123,17 @@ bool osq_lock(struct optimistic_spin_queue *lock) > while (!READ_ONCE(node->locked)) { > /* >* If we need to reschedule bail... so we can block. > + * An

Re: [PATCH 3/3] locking/osq: Drop the overload of osq_lock()

On Mon, Jun 27, 2016 at 01:41:30PM -0400, Pan Xinhui wrote: > @@ -118,8 +123,17 @@ bool osq_lock(struct optimistic_spin_queue *lock) > while (!READ_ONCE(node->locked)) { > /* >* If we need to reschedule bail... so we can block. > + * An

[PATCH 2/2] x86: vdso: use __pvclock_read_cycles

The new simplified __pvclock_read_cycles does the same computation as vread_pvclock, except that (because it takes the pvclock_vcpu_time_info pointer) it has to be moved inside the loop. Since the loop is expected to never roll, this makes no difference. Signed-off-by: Paolo Bonzini

[PATCH 2/2] x86: vdso: use __pvclock_read_cycles

The new simplified __pvclock_read_cycles does the same computation as vread_pvclock, except that (because it takes the pvclock_vcpu_time_info pointer) it has to be moved inside the loop. Since the loop is expected to never roll, this makes no difference. Signed-off-by: Paolo Bonzini ---

Re: [PATCH] MAINTAINERS: Update maintainer entry for wilc1000

On 27/06/16 15:10, Nicolas Ferre wrote: > From: Aditya Shankar > > Take the maintenance of the Atmel WIFI staging driver wilc1000. > Former maintainers are no more with Atmel. > > Reported-by: Loic Lefort > Signed-off-by: Aditya Shankar

Re: [PATCH] MAINTAINERS: Update maintainer entry for wilc1000

On 27/06/16 15:10, Nicolas Ferre wrote: > From: Aditya Shankar > > Take the maintenance of the Atmel WIFI staging driver wilc1000. > Former maintainers are no more with Atmel. > > Reported-by: Loic Lefort > Signed-off-by: Aditya Shankar > Signed-off-by: Ganesh Krishna > Signed-off-by:

[PATCH 1/2] pvclock: introduce seqcount-like API

The version field in struct pvclock_vcpu_time_info basically implements a seqcount. Wrap it with the usual read_begin and read_retry functions, and use these APIs instead of peppering the code with smp_rmb()s. While at it, change it to the more pedantically correct virt_rmb(). With this change,

[PATCH v3 0/2] pvclock: more code cleanup

Patch 1 simplifies the pvclock.h API by moving seqcount logic into two new functions pvclock_read_begin and pvclock_read_retry. Patch 2 uses the new simplified API in the vDSO. Please ack the vDSO changes! Paolo v2->v3: add unlikely() around read_retry check. Paolo Bonzini (2): pvclock:

[PATCH v3] x86/power/64: Fix kernel text mapping corruption during image restoration (was: Re: ktime_get_ts64() splat during resume)

On Tuesday, June 21, 2016 11:04:41 AM Kees Cook wrote: > On Mon, Jun 20, 2016 at 9:35 PM, Logan Gunthorpe wrote: > > Hey Rafael, > > > > This patch appears to be working on my laptop. Thanks. > > Same for me: resume still works with KASLR in my tests too. Unfortunately,

[PATCH 1/2] pvclock: introduce seqcount-like API

The version field in struct pvclock_vcpu_time_info basically implements a seqcount. Wrap it with the usual read_begin and read_retry functions, and use these APIs instead of peppering the code with smp_rmb()s. While at it, change it to the more pedantically correct virt_rmb(). With this change,

[PATCH v3 0/2] pvclock: more code cleanup

Patch 1 simplifies the pvclock.h API by moving seqcount logic into two new functions pvclock_read_begin and pvclock_read_retry. Patch 2 uses the new simplified API in the vDSO. Please ack the vDSO changes! Paolo v2->v3: add unlikely() around read_retry check. Paolo Bonzini (2): pvclock:

[PATCH v3] x86/power/64: Fix kernel text mapping corruption during image restoration (was: Re: ktime_get_ts64() splat during resume)

On Tuesday, June 21, 2016 11:04:41 AM Kees Cook wrote: > On Mon, Jun 20, 2016 at 9:35 PM, Logan Gunthorpe wrote: > > Hey Rafael, > > > > This patch appears to be working on my laptop. Thanks. > > Same for me: resume still works with KASLR in my tests too. Unfortunately, Boris still sees

[PATCH] mfd: arizona: Add missing disable of PM runtime on probe error path

Signed-off-by: Charles Keepax --- drivers/mfd/arizona-core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c index bf27179..e4f97b3 100644 --- a/drivers/mfd/arizona-core.c +++

[PATCH] mfd: arizona: Add missing disable of PM runtime on probe error path

Signed-off-by: Charles Keepax --- drivers/mfd/arizona-core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c index bf27179..e4f97b3 100644 --- a/drivers/mfd/arizona-core.c +++ b/drivers/mfd/arizona-core.c @@ -1462,7

Re: [PATCH 2/2] HID: multitouch: enable palm rejection for Windows Precision Touchpad

On Jun 23 2016 or thereabouts, Allen Hung wrote: > The usage Confidence is mandary to Windows Precision Touchpad devices. If > it is examined in input_mapping on a WIndows Precision Touchpad, a new add > quirk MT_QUIRK_CONFIDENCE desgned for such devices will be applied to the > device. A touch

Re: [PATCH 2/2] HID: multitouch: enable palm rejection for Windows Precision Touchpad

On Jun 23 2016 or thereabouts, Allen Hung wrote: > The usage Confidence is mandary to Windows Precision Touchpad devices. If > it is examined in input_mapping on a WIndows Precision Touchpad, a new add > quirk MT_QUIRK_CONFIDENCE desgned for such devices will be applied to the > device. A touch

Re: [PATCH] net: Fix resetting network_header in neigh_resolve_output and neigh_connected_output

From: Abdelrhman Ahmed Date: Thu, 23 Jun 2016 13:39:24 +0200 > neigh_resolve_output and neigh_connected_output resets the skb to > network_header because of the retry loop and this reset will pull down the > data pointer to the network header in the first iteration then

Re: [PATCH] net: Fix resetting network_header in neigh_resolve_output and neigh_connected_output

From: Abdelrhman Ahmed Date: Thu, 23 Jun 2016 13:39:24 +0200 > neigh_resolve_output and neigh_connected_output resets the skb to > network_header because of the retry loop and this reset will pull down the > data pointer to the network header in the first iteration then hardware > header will

Re: [PATCH 2/3] powerpc/spinlock: support vcpu preempted check

On Mon, Jun 27, 2016 at 01:41:29PM -0400, Pan Xinhui wrote: > diff --git a/arch/powerpc/include/asm/spinlock.h > b/arch/powerpc/include/asm/spinlock.h > index 523673d..ae938ee 100644 > --- a/arch/powerpc/include/asm/spinlock.h > +++ b/arch/powerpc/include/asm/spinlock.h > @@ -52,6 +52,21 @@ >

Re: [PATCH 2/3] powerpc/spinlock: support vcpu preempted check

On Mon, Jun 27, 2016 at 01:41:29PM -0400, Pan Xinhui wrote: > diff --git a/arch/powerpc/include/asm/spinlock.h > b/arch/powerpc/include/asm/spinlock.h > index 523673d..ae938ee 100644 > --- a/arch/powerpc/include/asm/spinlock.h > +++ b/arch/powerpc/include/asm/spinlock.h > @@ -52,6 +52,21 @@ >

Re: [PATCH v4 5/8] spi: add support for ACPI reconfigure notifications

On Fri, Jun 17, 2016 at 02:52:13PM +0300, Octavian Purdila wrote: > This patch adds supports for SPI device enumeration and removal via > ACPI reconfiguration notifications that are send as a result of an > ACPI table load or unload operation. I still have the same concern I've had all the way

Re: [PATCH v4 5/8] spi: add support for ACPI reconfigure notifications

On Fri, Jun 17, 2016 at 02:52:13PM +0300, Octavian Purdila wrote: > This patch adds supports for SPI device enumeration and removal via > ACPI reconfiguration notifications that are send as a result of an > ACPI table load or unload operation. I still have the same concern I've had all the way

Re: [PATCH v2 0/2] pvclock: more code cleanup

On 15/06/2016 14:46, Paolo Bonzini wrote: > Patch 1 simplifies the pvclock.h API by moving seqcount logic into > two new functions pvclock_read_begin and pvclock_read_retry. > Patch 2 uses the new simplified API in the vDSO. Andy, I've now benchmarked the patches. Patch 2 introduces no

Re: [PATCH v2 0/2] pvclock: more code cleanup

On 15/06/2016 14:46, Paolo Bonzini wrote: > Patch 1 simplifies the pvclock.h API by moving seqcount logic into > two new functions pvclock_read_begin and pvclock_read_retry. > Patch 2 uses the new simplified API in the vDSO. Andy, I've now benchmarked the patches. Patch 2 introduces no

[PATCH] ARM: dts: da850: Add new ECAP and EPWM bindings

From: "Cooper Jr., Franklin" Switch to a new ECAP and EPWM bindings that doesn't depend on hwmod to provide the various required clocks. Signed-off-by: Franklin S Cooper Jr Acked-by: Rob Herring --- This patch is a da850 specific version of:

[PATCH] ARM: dts: da850: Add new ECAP and EPWM bindings

From: "Cooper Jr., Franklin" Switch to a new ECAP and EPWM bindings that doesn't depend on hwmod to provide the various required clocks. Signed-off-by: Franklin S Cooper Jr Acked-by: Rob Herring --- This patch is a da850 specific version of: ARM: dts: am437x/am33xx/da850: Add new ECAP and

[PATCH] MAINTAINERS: Update maintainer entry for wilc1000

From: Aditya Shankar Take the maintenance of the Atmel WIFI staging driver wilc1000. Former maintainers are no more with Atmel. Reported-by: Loic Lefort Signed-off-by: Aditya Shankar Signed-off-by: Ganesh

[PATCH] MAINTAINERS: Update maintainer entry for wilc1000

From: Aditya Shankar Take the maintenance of the Atmel WIFI staging driver wilc1000. Former maintainers are no more with Atmel. Reported-by: Loic Lefort Signed-off-by: Aditya Shankar Signed-off-by: Ganesh Krishna Signed-off-by: Nicolas Ferre --- Hi Luis, Greg, I'd like that we don't

Re: [PATCH 1/5] spi: do not fail if the CS line is not connected

Hi Mark, > > What I meant is that if we do not like num-cs = <0>, the > > unlinked CS line can be handled only this way (case of the > > s3c64xx driver): > > > +- broken-cs: the CS line is disconnected, therefore the device should not > > wait > > + for the CS protocol to be established > >

Re: [PATCH 1/5] spi: do not fail if the CS line is not connected

Hi Mark, > > What I meant is that if we do not like num-cs = <0>, the > > unlinked CS line can be handled only this way (case of the > > s3c64xx driver): > > > +- broken-cs: the CS line is disconnected, therefore the device should not > > wait > > + for the CS protocol to be established > >

Re: [tpmdd-devel] [PATCH] tpm: use devm_add_action_or_reset

On Thu, Jun 16, 2016 at 10:28:23PM +0200, Jarkko Sakkinen wrote: > On Sun, Jun 12, 2016 at 03:05:29PM +0100, Sudip Mukherjee wrote: > > If devm_add_action() fails we are explicitly calling put_device() to > > free the resources allocated. Lets use the helper > > devm_add_action_or_reset() and

Re: [tpmdd-devel] [PATCH] tpm: use devm_add_action_or_reset

On Thu, Jun 16, 2016 at 10:28:23PM +0200, Jarkko Sakkinen wrote: > On Sun, Jun 12, 2016 at 03:05:29PM +0100, Sudip Mukherjee wrote: > > If devm_add_action() fails we are explicitly calling put_device() to > > free the resources allocated. Lets use the helper > > devm_add_action_or_reset() and

Re: [PATCH v14 04/10] arm64: Kprobes with single stepping support

On 06/27/2016 02:57 AM, Pratyush Anand wrote: Hi David, On 26/06/2016:11:06:47 PM, David Long wrote: From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step

Re: [PATCH v14 04/10] arm64: Kprobes with single stepping support

On 06/27/2016 02:57 AM, Pratyush Anand wrote: Hi David, On 26/06/2016:11:06:47 PM, David Long wrote: From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM

Re: [PATCH 1/3] kernel/sched: introduce vcpu preempted check interface

On Mon, Jun 27, 2016 at 04:00:43PM +0200, Peter Zijlstra wrote: > On Mon, Jun 27, 2016 at 01:41:28PM -0400, Pan Xinhui wrote: > > +++ b/include/linux/sched.h > > @@ -3293,6 +3293,15 @@ static inline void set_task_cpu(struct task_struct > > *p, unsigned int cpu) > > > > #endif /* CONFIG_SMP */

Re: [PATCH 1/3] kernel/sched: introduce vcpu preempted check interface

On Mon, Jun 27, 2016 at 04:00:43PM +0200, Peter Zijlstra wrote: > On Mon, Jun 27, 2016 at 01:41:28PM -0400, Pan Xinhui wrote: > > +++ b/include/linux/sched.h > > @@ -3293,6 +3293,15 @@ static inline void set_task_cpu(struct task_struct > > *p, unsigned int cpu) > > > > #endif /* CONFIG_SMP */

Re: [PATCH 1/3] kernel/sched: introduce vcpu preempted check interface

On Mon, Jun 27, 2016 at 01:41:28PM -0400, Pan Xinhui wrote: > this supports to fix lock holder preempted issue which run as a guest > > for kernel users, we could use bool vcpu_is_preempted(int cpu) to detech > if one vcpu is preempted or not. > > The default implementation is a macrodefined by

Re: [PATCH 1/3] kernel/sched: introduce vcpu preempted check interface

On Mon, Jun 27, 2016 at 01:41:28PM -0400, Pan Xinhui wrote: > this supports to fix lock holder preempted issue which run as a guest > > for kernel users, we could use bool vcpu_is_preempted(int cpu) to detech > if one vcpu is preempted or not. > > The default implementation is a macrodefined by

Re: [PATCH 1/3] kernel/sched: introduce vcpu preempted check interface

On Mon, Jun 27, 2016 at 01:41:28PM -0400, Pan Xinhui wrote: > +++ b/include/linux/sched.h > @@ -3293,6 +3293,15 @@ static inline void set_task_cpu(struct task_struct *p, > unsigned int cpu) > > #endif /* CONFIG_SMP */ > > +#ifdef arch_vcpu_is_preempted > +static inline bool

Re: [PATCH 1/3] kernel/sched: introduce vcpu preempted check interface

On Mon, Jun 27, 2016 at 01:41:28PM -0400, Pan Xinhui wrote: > +++ b/include/linux/sched.h > @@ -3293,6 +3293,15 @@ static inline void set_task_cpu(struct task_struct *p, > unsigned int cpu) > > #endif /* CONFIG_SMP */ > > +#ifdef arch_vcpu_is_preempted > +static inline bool

[PATCH] [perf]: update makefile message for installing required libs

From: Neeraj Badlani In case of missing library (libslang), give hint to install library (libslang2-dev) Since libslang-dev is not provided by Ubuntu's apt-package Signed-off-by: Neeraj Badlani --- tools/perf/config/Makefile | 2 +- 1 file

[PATCH] [perf]: update makefile message for installing required libs

From: Neeraj Badlani In case of missing library (libslang), give hint to install library (libslang2-dev) Since libslang-dev is not provided by Ubuntu's apt-package Signed-off-by: Neeraj Badlani --- tools/perf/config/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/4] ftrace/x86: Make sure to modify 5-bite instructions

The commit 8329e818f14926a604 ("ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it") fixed a situation where we replaced 2-byte with 5-byte jump instruction. The original problem crashed the kernel with # cd /sys/kernel/trace # echo function_graph >

[PATCH 1/4] ftrace/x86: Make sure to modify 5-bite instructions

The commit 8329e818f14926a604 ("ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it") fixed a situation where we replaced 2-byte with 5-byte jump instruction. The original problem crashed the kernel with # cd /sys/kernel/trace # echo function_graph >

Re: [PATCH] tipc: Use kmemdup instead of kmalloc and memcpy

From: Amitoj Kaur Chawla Date: Thu, 23 Jun 2016 10:19:37 +0530 > Replace calls to kmalloc followed by a memcpy with a direct call to > kmemdup. > > The Coccinelle semantic patch used to make this change is as follows: > @@ > expression from,to,size,flag; > statement S; >

Re: [PATCH] tipc: Use kmemdup instead of kmalloc and memcpy

From: Amitoj Kaur Chawla Date: Thu, 23 Jun 2016 10:19:37 +0530 > Replace calls to kmalloc followed by a memcpy with a direct call to > kmemdup. > > The Coccinelle semantic patch used to make this change is as follows: > @@ > expression from,to,size,flag; > statement S; > @@ > > - to =

[PATCH] devfreq: Add COMPILE_TEST for build coverage

The SoC-specific devfreq and event drivers can be build tested on all architectures. Signed-off-by: Krzysztof Kozlowski --- Success of compilation tested on ARM, ARM64, i386, x86_64 and powerpc architectures (allyesconfigs). --- drivers/devfreq/Kconfig | 4 ++--

[PATCH] devfreq: Add COMPILE_TEST for build coverage

The SoC-specific devfreq and event drivers can be build tested on all architectures. Signed-off-by: Krzysztof Kozlowski --- Success of compilation tested on ARM, ARM64, i386, x86_64 and powerpc architectures (allyesconfigs). --- drivers/devfreq/Kconfig | 4 ++--

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