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: > 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 this respect well before > >any of the drivers

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: > 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 this respect well before > >any of the drivers

[PATCH 2/2]staging:vt6656:dpc.c:Fix spaces

The following patch fixes two checks thrown by checkpatch.pl, "Spaces preferred around '+'" and "No space is necessary after a cast" Signed-off-by: Rithvik Patibandla --- drivers/staging/vt6656/dpc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 1/1] drivers:iio:light:isl29125: added macros for sensing range

> On 24/06/16 12:16, Bijosh Thykkoottathil wrote: > > Added macros for sensing range as the corresponding magic numbers > > were used at multiple places. > >- SENSING_RANGE_0 for 375 lux full range > >- SENSING_RANGE_1 for 10k lux full range > Macros are great for making cases of 'magic

[PATCH 2/2]staging:vt6656:dpc.c:Fix spaces

The following patch fixes two checks thrown by checkpatch.pl, "Spaces preferred around '+'" and "No space is necessary after a cast" Signed-off-by: Rithvik Patibandla --- drivers/staging/vt6656/dpc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 1/1] drivers:iio:light:isl29125: added macros for sensing range

> On 24/06/16 12:16, Bijosh Thykkoottathil wrote: > > Added macros for sensing range as the corresponding magic numbers > > were used at multiple places. > >- SENSING_RANGE_0 for 375 lux full range > >- SENSING_RANGE_1 for 10k lux full range > Macros are great for making cases of 'magic

[PATCH v2] printk: introduce suppress_message_printing()

Messages' levels and console log level are inspected when the actual printing occurs, which may provoke console_unlock() and console_cont_flush() to waste CPU cycles on every message that has loglevel above the current console_loglevel. Schematically, console_unlock() does the following:

[PATCH v2] printk: introduce suppress_message_printing()

Messages' levels and console log level are inspected when the actual printing occurs, which may provoke console_unlock() and console_cont_flush() to waste CPU cycles on every message that has loglevel above the current console_loglevel. Schematically, console_unlock() does the following:

[PATCH 4/4] ftrace: Fixup trace_selftest_ops()

I was hunting a memory leak related to trace_selftest_ops() and found two small mistakes there. First, the dynamic trace must be freed in case of error. There was one wrong goto target. It was even in the original commit 95950c2ecb31314ef ("ftrace: Add self-tests for multiple function trace

[PATCH 4/4] ftrace: Fixup trace_selftest_ops()

I was hunting a memory leak related to trace_selftest_ops() and found two small mistakes there. First, the dynamic trace must be freed in case of error. There was one wrong goto target. It was even in the original commit 95950c2ecb31314ef ("ftrace: Add self-tests for multiple function trace

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

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(). It is true that this function is used only to modify well defined

[PATCH 0/4] ftrace: One more check on x86 and some small fixes

1st patch adds one more paranoid check of the modified function on x86. Plus there are 3 small changes that appeared when hunting down the 1st patch. Petr Mladek (4): ftrace/x86: Make sure to modify 5-bite instructions ftrace/x86: Do not crash when reading wrong ftrace func ftrace: Always

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

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(). It is true that this function is used only to modify well defined

[PATCH 0/4] ftrace: One more check on x86 and some small fixes

1st patch adds one more paranoid check of the modified function on x86. Plus there are 3 small changes that appeared when hunting down the 1st patch. Petr Mladek (4): ftrace/x86: Make sure to modify 5-bite instructions ftrace/x86: Do not crash when reading wrong ftrace func ftrace: Always

[PATCH 3/4] ftrace: Always destroy trampoline when shutting down the trace

If have got the following kmemleak report when I enabled the ftrace self test: unreferenced object 0xa000a000 (size 179): comm "swapper/0", pid 1, jiffies 4294892507 (age 82553.780s) hex dump (first 32 bytes): 55 ff 74 24 10 55 48 89 e5 ff 74 24 18 55 48 89 U.t$.UH...t$.UH.

[PATCH 3/4] ftrace: Always destroy trampoline when shutting down the trace

If have got the following kmemleak report when I enabled the ftrace self test: unreferenced object 0xa000a000 (size 179): comm "swapper/0", pid 1, jiffies 4294892507 (age 82553.780s) hex dump (first 32 bytes): 55 ff 74 24 10 55 48 89 e5 ff 74 24 18 55 48 89 U.t$.UH...t$.UH.

[PATCH 1/2]staging:vt6656:dpc.c:Fix parantheses alignment

This patch fixes "Alignment should match open parantheses" check thrown by checkpatch.pl Signed-off-by: Rithvik Patibandla --- drivers/staging/vt6656/dpc.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/vt6656/dpc.c

[PATCH 1/2]staging:vt6656:dpc.c:Fix parantheses alignment

This patch fixes "Alignment should match open parantheses" check thrown by checkpatch.pl Signed-off-by: Rithvik Patibandla --- drivers/staging/vt6656/dpc.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/vt6656/dpc.c b/drivers/staging/vt6656/dpc.c

Re: [PATCHv3 1/2] usb: USB Type-C connector class

On 06/27/2016 05:13 AM, Heikki Krogerus wrote: Hi, On Mon, Jun 27, 2016 at 03:51:08PM +0530, Rajaram R wrote: May be I am missing user or usage of the driver.. I see this driver is providing limited information of the Type-C connectors or the port partner Yes, this interface can't provide

Re: [PATCHv3 1/2] usb: USB Type-C connector class

On 06/27/2016 05:13 AM, Heikki Krogerus wrote: Hi, On Mon, Jun 27, 2016 at 03:51:08PM +0530, Rajaram R wrote: May be I am missing user or usage of the driver.. I see this driver is providing limited information of the Type-C connectors or the port partner Yes, this interface can't provide

Re: [PATCH 1/2] mm: CONFIG_ZONE_DEVICE stop depending on CONFIG_EXPERT

Dan Williams writes: > When it was first introduced CONFIG_ZONE_DEVICE depended on disabling > CONFIG_ZONE_DMA, a configuration choice reserved for "experts". > However, now that the ZONE_DMA conflict has been eliminated it no longer > makes sense to require

Re: [PATCH 1/2] mm: CONFIG_ZONE_DEVICE stop depending on CONFIG_EXPERT

Dan Williams writes: > When it was first introduced CONFIG_ZONE_DEVICE depended on disabling > CONFIG_ZONE_DMA, a configuration choice reserved for "experts". > However, now that the ZONE_DMA conflict has been eliminated it no longer > makes sense to require CONFIG_EXPERT. > > Reported-by: Eric

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

An over-committed guest with more vCPUs than pCPUs has a heavy overload in osq_lock(). This is because vCPU A hold the osq lock and yield out, vCPU B wait per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and unlock the osq lock. Such spinning is meaningless. So lets use

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

An over-committed guest with more vCPUs than pCPUs has a heavy overload in osq_lock(). This is because vCPU A hold the osq lock and yield out, vCPU B wait per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and unlock the osq lock. Such spinning is meaningless. So lets use

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

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. So add lppaca_dedicated_proc macro in lppaca.h Suggested-by: Boqun Feng

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

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 false. So compiler can wrap it out if arch dose not support such vcpu

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

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. So add lppaca_dedicated_proc macro in lppaca.h Suggested-by: Boqun Feng

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

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 false. So compiler can wrap it out if arch dose not support such vcpu

[PATCH 0/3] implement vcpu preempted check

This is to fix some bad issues on an over-committed guest. test-caes: perf record -a perf bench sched messaging -g 400 -p && perf report 18.09% sched-messaging [kernel.vmlinux] [k] osq_lock 12.28% sched-messaging [kernel.vmlinux] [k] rwsem_spin_on_owner 5.27% sched-messaging

[PATCH 0/3] implement vcpu preempted check

This is to fix some bad issues on an over-committed guest. test-caes: perf record -a perf bench sched messaging -g 400 -p && perf report 18.09% sched-messaging [kernel.vmlinux] [k] osq_lock 12.28% sched-messaging [kernel.vmlinux] [k] rwsem_spin_on_owner 5.27% sched-messaging

[PATCH v2] wlcore: time sync : add support for 64 bit clock

Changed the configuration to support 64bit instead of 32bit this in order to offload the driver from handling a wraparound. Signed-off-by: Yaniv Machani --- V2 - Update the interface parameters type to le16 from u16. drivers/net/wireless/ti/wl18xx/event.c | 26

[PATCH v2] wlcore: time sync : add support for 64 bit clock

Changed the configuration to support 64bit instead of 32bit this in order to offload the driver from handling a wraparound. Signed-off-by: Yaniv Machani --- V2 - Update the interface parameters type to le16 from u16. drivers/net/wireless/ti/wl18xx/event.c | 26 +-

Re: [PATCH] xen-blkfront: save uncompleted reqs in blkfront_resume()

On 06/27/2016 04:33 PM, Bob Liu wrote: > Uncompleted reqs used to be 'saved and resubmitted' in blkfront_recover() > during > migration, but that's too later after multi-queue introduced. > > After a migrate to another host (which may not have multiqueue support), the > number of rings (block

Re: [PATCH] xen-blkfront: save uncompleted reqs in blkfront_resume()

On 06/27/2016 04:33 PM, Bob Liu wrote: > Uncompleted reqs used to be 'saved and resubmitted' in blkfront_recover() > during > migration, but that's too later after multi-queue introduced. > > After a migrate to another host (which may not have multiqueue support), the > number of rings (block

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

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 >> called regs for PMIC chip - regs op region is used

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

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 >> called regs for PMIC chip - regs op region is used to handle the >> PMIC gpio mainly

Re: [PATCH] ARM: STi: Update machine _namestr to be more generic.

Hi Peter On 05/11/2016 06:40 PM, Peter Griffin wrote: This string is used by dump_stack and as we now support more SoC's than just STiH415/6 it is misleading to have the current string in the stack trace. This patch updates it to be more generic for the STi family of SoCs. So instead of

Re: [PATCH] ARM: STi: Update machine _namestr to be more generic.

Hi Peter On 05/11/2016 06:40 PM, Peter Griffin wrote: This string is used by dump_stack and as we now support more SoC's than just STiH415/6 it is misleading to have the current string in the stack trace. This patch updates it to be more generic for the STi family of SoCs. So instead of

[PATCH v2] fujitsu-laptop: Support touchpad toggle hotkey on Skylake-based models

Haswell-based Fujitsu laptops (Lifebook E734/E744/E754) have a touchpad toggle hotkey (Fn+F4) which is handled transparently to the operating system: while an ACPI notification is sent to FUJ02B1 when Fn+F4 is pressed, touchpad state is properly toggled without any explicit support for this

[PATCH v2] fujitsu-laptop: Support touchpad toggle hotkey on Skylake-based models

Haswell-based Fujitsu laptops (Lifebook E734/E744/E754) have a touchpad toggle hotkey (Fn+F4) which is handled transparently to the operating system: while an ACPI notification is sent to FUJ02B1 when Fn+F4 is pressed, touchpad state is properly toggled without any explicit support for this

Re: [PATCH] dt-bindings: i2c: add bindings for nxp,pca9541

On 06/27/2016 03:11 AM, Peter Rosin wrote: Fill the gap for this pre-existing driver. Signed-off-by: Peter Rosin --- .../devicetree/bindings/i2c/i2c-arb-pca9541.txt| 33 ++ MAINTAINERS| 1 + 2 files changed,

Re: [PATCH] dt-bindings: i2c: add bindings for nxp,pca9541

On 06/27/2016 03:11 AM, Peter Rosin wrote: Fill the gap for this pre-existing driver. Signed-off-by: Peter Rosin --- .../devicetree/bindings/i2c/i2c-arb-pca9541.txt| 33 ++ MAINTAINERS| 1 + 2 files changed, 34 insertions(+)

[PATCH v3] MAINTAINERS: remove unreachable people that have left Atmel

When sending an email regarding a patch to wilc1000, you get the following automatic replies: "Sung_hoon Cho is no longer with Atmel Corporation." "Kang_hee Park is no longer with Atmel Corporation." "Dong_ho Shin is no longer with Atmel Corporation." "Bo_moon Kim is no longer with Atmel

[PATCH v3] MAINTAINERS: remove unreachable people that have left Atmel

When sending an email regarding a patch to wilc1000, you get the following automatic replies: "Sung_hoon Cho is no longer with Atmel Corporation." "Kang_hee Park is no longer with Atmel Corporation." "Dong_ho Shin is no longer with Atmel Corporation." "Bo_moon Kim is no longer with Atmel

Re: Freeing active kobject in pps_device_destruct

On Sat, 25 Jun 2016, Vegard Nossum wrote: > On 27 November 2015 at 05:30, Sasha Levin wrote: > > (active state 0) object type: timer_list hint: > > delayed_work_timer_fn+0x0/0x90 > > [ 1167.394563] Workqueue: events kobject_delayed_cleanup > > [ 1167.410301] []

Re: Freeing active kobject in pps_device_destruct

On Sat, 25 Jun 2016, Vegard Nossum wrote: > On 27 November 2015 at 05:30, Sasha Levin wrote: > > (active state 0) object type: timer_list hint: > > delayed_work_timer_fn+0x0/0x90 > > [ 1167.394563] Workqueue: events kobject_delayed_cleanup > > [ 1167.410301] [] kfree+0x1fc/0x2f0 > > [

Re: [PATCH] Decouple CFG and IO in Designware PCIe Driver

Hi, all. How about exchanging the assignments of `MEMORYs' and `CFGs/IOs'? In other words, assign MEMEORYs to iatu0, CFGs and IOs to iatu1. Once the iatu0 is initialized to MEMORY accesses, its BASE_ADDR, LIMIT and TYPE is fixed. MEMORYs match with iatu0 at first, so they will never being

Re: [PATCH] Decouple CFG and IO in Designware PCIe Driver

Hi, all. How about exchanging the assignments of `MEMORYs' and `CFGs/IOs'? In other words, assign MEMEORYs to iatu0, CFGs and IOs to iatu1. Once the iatu0 is initialized to MEMORY accesses, its BASE_ADDR, LIMIT and TYPE is fixed. MEMORYs match with iatu0 at first, so they will never being

[PATCH] KVM: vmx: fix underflow in TSC deadline calculation

If the TSC deadline timer is programmed really close to the deadline or even in the past, the computation in vmx_set_hv_timer can underflow and cause delta_tsc to be set to a huge value. This generally results in vmx_set_hv_timer returning -ERANGE, but we can fix it by limiting delta_tsc to be

[PATCH] KVM: vmx: fix underflow in TSC deadline calculation

If the TSC deadline timer is programmed really close to the deadline or even in the past, the computation in vmx_set_hv_timer can underflow and cause delta_tsc to be set to a huge value. This generally results in vmx_set_hv_timer returning -ERANGE, but we can fix it by limiting delta_tsc to be

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

On Mon, Jun 27, 2016 at 07:57:16PM +0900, Andi Shyti wrote: > 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

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

On Mon, Jun 27, 2016 at 07:57:16PM +0900, Andi Shyti wrote: > 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

Re: [PATCH] usb: ulpi: Automatically set driver::owner with ulpi_driver_register()

On Sat, Jun 25, 2016 at 10:38:21PM -0700, Stephen Boyd wrote: > Let's follow other driver registration functions and > automatically set the driver's owner member to THIS_MODULE when > ulpi_driver_register() is called. This allows ulpi driver writers > to forget about this boiler plate detail and

Re: [PATCH] usb: ulpi: Automatically set driver::owner with ulpi_driver_register()

On Sat, Jun 25, 2016 at 10:38:21PM -0700, Stephen Boyd wrote: > Let's follow other driver registration functions and > automatically set the driver's owner member to THIS_MODULE when > ulpi_driver_register() is called. This allows ulpi driver writers > to forget about this boiler plate detail and

[RFC] Can we bypass the timeout when resetting Synaptics device?

Hi All, Currently I'm doing some tunings on the speed of suspend/resume, it looks like my serio driver tooks a 200ms to finish, which is too long: [ 1120.255783] calling serio0+ @ 2764, parent: i8042 [ 1120.452976] call serio0+ returned 0 after 192472 usecs So further investigation shows that

Re: [PATCH rebase] mm: fix vm-scalability regression in cgroup-aware workingset code

[Sorry for a late reply] On Fri 24-06-16 13:51:01, Johannes Weiner wrote: > This is a rebased version on top of mmots sans the nodelru stuff. > > --- > > 23047a96d7cf ("mm: workingset: per-cgroup cache thrash detection") > added a page->mem_cgroup lookup to the cache eviction, refault, and >

[RFC] Can we bypass the timeout when resetting Synaptics device?

Hi All, Currently I'm doing some tunings on the speed of suspend/resume, it looks like my serio driver tooks a 200ms to finish, which is too long: [ 1120.255783] calling serio0+ @ 2764, parent: i8042 [ 1120.452976] call serio0+ returned 0 after 192472 usecs So further investigation shows that

Re: [PATCH rebase] mm: fix vm-scalability regression in cgroup-aware workingset code

[Sorry for a late reply] On Fri 24-06-16 13:51:01, Johannes Weiner wrote: > This is a rebased version on top of mmots sans the nodelru stuff. > > --- > > 23047a96d7cf ("mm: workingset: per-cgroup cache thrash detection") > added a page->mem_cgroup lookup to the cache eviction, refault, and >

[tip:efi/core] x86/efi: Remove the unused efi_get_time() function

Commit-ID: b684e9bc750b6349ff59f1b1ab4397cae255765f Gitweb: http://git.kernel.org/tip/b684e9bc750b6349ff59f1b1ab4397cae255765f Author: Arnd Bergmann AuthorDate: Sat, 25 Jun 2016 08:20:30 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:58

Re: kernel-4.7 bug in Intel sound and/or ACPI

On Mon, Jun 27, 2016 at 04:22:18AM -0400, ok...@codeaurora.org wrote: > > However, an earlier try on my Inspiron 510m did not work. > > I'll do a clean retry later today, just to make sure. > > > Ok, let me know. I can post a clean patch series. I was trying to get > you something to test

[tip:efi/core] x86/efi: Remove the unused efi_get_time() function

Commit-ID: b684e9bc750b6349ff59f1b1ab4397cae255765f Gitweb: http://git.kernel.org/tip/b684e9bc750b6349ff59f1b1ab4397cae255765f Author: Arnd Bergmann AuthorDate: Sat, 25 Jun 2016 08:20:30 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:58 +0200 x86/efi: Remove the

Re: kernel-4.7 bug in Intel sound and/or ACPI

On Mon, Jun 27, 2016 at 04:22:18AM -0400, ok...@codeaurora.org wrote: > > However, an earlier try on my Inspiron 510m did not work. > > I'll do a clean retry later today, just to make sure. > > > Ok, let me know. I can post a clean patch series. I was trying to get > you something to test

RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

Ping!! > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Friday, June 03, 2016 4:28 AM > To: Nava kishore Manne > Cc: pawel.m...@arm.com; mark.rutl...@arm.com; > ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; Michal Simek >

Re: [PATCH] printk: introduce should_ignore_loglevel()

On (06/27/16 11:26), Petr Mladek wrote: > On Sat 2016-06-25 14:22:37, Sergey Senozhatsky wrote: > > On (06/24/16 18:05), Petr Mladek wrote: > > [..] > > > > +static bool should_ignore_loglevel(int level) > > > > +{ > > > > + return (level >= console_loglevel && !ignore_loglevel); > > > > >

RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

Ping!! > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Friday, June 03, 2016 4:28 AM > To: Nava kishore Manne > Cc: pawel.m...@arm.com; mark.rutl...@arm.com; > ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; Michal Simek > ; Soren Brinkmann ; >

Re: [PATCH] printk: introduce should_ignore_loglevel()

On (06/27/16 11:26), Petr Mladek wrote: > On Sat 2016-06-25 14:22:37, Sergey Senozhatsky wrote: > > On (06/24/16 18:05), Petr Mladek wrote: > > [..] > > > > +static bool should_ignore_loglevel(int level) > > > > +{ > > > > + return (level >= console_loglevel && !ignore_loglevel); > > > > >

[tip:efi/core] efi: Convert efi_call_virt() to efi_call_virt_pointer()

Commit-ID: 80e75596079f0a41f905836ad0ccaac68ba33612 Gitweb: http://git.kernel.org/tip/80e75596079f0a41f905836ad0ccaac68ba33612 Author: Alex Thorlton AuthorDate: Sat, 25 Jun 2016 08:20:27 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016

[tip:efi/core] x86/efi: Update efi_thunk() to use the the arch_efi_call_virt*() macros

Commit-ID: 21f866257c7027f8f49bfde83f559f9e58f9ee93 Gitweb: http://git.kernel.org/tip/21f866257c7027f8f49bfde83f559f9e58f9ee93 Author: Alex Thorlton AuthorDate: Sat, 25 Jun 2016 08:20:29 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016

[PATCH v2 1/2] clk: exynos5433: do not use CLK_IGNORE_UNUSED for SPI clocks

The CLK_IGNORE_UNUSED flag has to be avoided whenever possible. Use the CLK_IS_CRITICAL flag instead, which enables the clock line during boot time. While none of the SCLK_SPI need to be alive all the time as that clock is handled by the SPI driver as a busclk whenever needed. Suggested-by:

[PATCH v2 2/2] clk: exynos5433: enable sclk_ioclk for SPI3

enable SPI3 iosclk by using the CLK_IS_CRITICAL flag. There is no device which is supposed to enable this clock when needed, therefore, the only way to use the SPI bus is to enable it in boot time. Suggested-by: Tomasz Figa Signed-off-by: Andi Shyti

[tip:efi/core] x86/uv: Update uv_bios_call() to use efi_call_virt_pointer()

Commit-ID: d1be84a232e359ca9456c63e72cb0082d68311b6 Gitweb: http://git.kernel.org/tip/d1be84a232e359ca9456c63e72cb0082d68311b6 Author: Alex Thorlton AuthorDate: Sat, 25 Jun 2016 08:20:28 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016

[tip:efi/core] x86/efi: Update efi_thunk() to use the the arch_efi_call_virt*() macros

Commit-ID: 21f866257c7027f8f49bfde83f559f9e58f9ee93 Gitweb: http://git.kernel.org/tip/21f866257c7027f8f49bfde83f559f9e58f9ee93 Author: Alex Thorlton AuthorDate: Sat, 25 Jun 2016 08:20:29 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:57 +0200 x86/efi: Update

[PATCH v2 1/2] clk: exynos5433: do not use CLK_IGNORE_UNUSED for SPI clocks

The CLK_IGNORE_UNUSED flag has to be avoided whenever possible. Use the CLK_IS_CRITICAL flag instead, which enables the clock line during boot time. While none of the SCLK_SPI need to be alive all the time as that clock is handled by the SPI driver as a busclk whenever needed. Suggested-by:

[PATCH v2 2/2] clk: exynos5433: enable sclk_ioclk for SPI3

enable SPI3 iosclk by using the CLK_IS_CRITICAL flag. There is no device which is supposed to enable this clock when needed, therefore, the only way to use the SPI bus is to enable it in boot time. Suggested-by: Tomasz Figa Signed-off-by: Andi Shyti Signed-off-by: Jaehoon Chung --- Hi, V1 ->

[tip:efi/core] x86/uv: Update uv_bios_call() to use efi_call_virt_pointer()

Commit-ID: d1be84a232e359ca9456c63e72cb0082d68311b6 Gitweb: http://git.kernel.org/tip/d1be84a232e359ca9456c63e72cb0082d68311b6 Author: Alex Thorlton AuthorDate: Sat, 25 Jun 2016 08:20:28 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:56 +0200 x86/uv: Update

[tip:efi/core] efi: Convert efi_call_virt() to efi_call_virt_pointer()

Commit-ID: 80e75596079f0a41f905836ad0ccaac68ba33612 Gitweb: http://git.kernel.org/tip/80e75596079f0a41f905836ad0ccaac68ba33612 Author: Alex Thorlton AuthorDate: Sat, 25 Jun 2016 08:20:27 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:56 +0200 efi: Convert

Re: [PATCH v2 1/2] staging: wilc1000: fix error handling in wilc_debugfs_init()

On 25/06/16 23:16, Greg KH wrote: > On Sat, Jun 25, 2016 at 10:43:33PM +0100, Luis de Bethencourt wrote: >> On 25/06/16 22:36, Greg KH wrote: >>> On Thu, Jun 23, 2016 at 01:36:17PM +0100, Luis de Bethencourt wrote: The common format to check if a function returned an error pointer is to

Re: [PATCH v2 1/2] staging: wilc1000: fix error handling in wilc_debugfs_init()

On 25/06/16 23:16, Greg KH wrote: > On Sat, Jun 25, 2016 at 10:43:33PM +0100, Luis de Bethencourt wrote: >> On 25/06/16 22:36, Greg KH wrote: >>> On Thu, Jun 23, 2016 at 01:36:17PM +0100, Luis de Bethencourt wrote: The common format to check if a function returned an error pointer is to

[tip:efi/core] x86/efi: Remove unused variable 'efi'

Commit-ID: f6d1747f898cfe1fe52e3d18f5c77e5bd21fed9a Gitweb: http://git.kernel.org/tip/f6d1747f898cfe1fe52e3d18f5c77e5bd21fed9a Author: Colin Ian King AuthorDate: Sat, 25 Jun 2016 08:20:26 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun

[tip:efi/core] x86/efi: Remove unused variable 'efi'

Commit-ID: f6d1747f898cfe1fe52e3d18f5c77e5bd21fed9a Gitweb: http://git.kernel.org/tip/f6d1747f898cfe1fe52e3d18f5c77e5bd21fed9a Author: Colin Ian King AuthorDate: Sat, 25 Jun 2016 08:20:26 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:55 +0200 x86/efi: Remove unused

[tip:efi/core] efibc: Report more information in the error messages

Commit-ID: 5356c32742bd51c8c57065d2389a2c4bc036adcd Gitweb: http://git.kernel.org/tip/5356c32742bd51c8c57065d2389a2c4bc036adcd Author: Compostella, Jeremy AuthorDate: Sat, 25 Jun 2016 08:20:24 +0100 Committer: Ingo Molnar CommitDate: Mon,

[tip:efi/core] efibc: Report more information in the error messages

Commit-ID: 5356c32742bd51c8c57065d2389a2c4bc036adcd Gitweb: http://git.kernel.org/tip/5356c32742bd51c8c57065d2389a2c4bc036adcd Author: Compostella, Jeremy AuthorDate: Sat, 25 Jun 2016 08:20:24 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:54 +0200 efibc: Report more

[tip:efi/core] efi: Document #define FOO_PROTOCOL_GUID layout

Commit-ID: 54fd11fee59e7d05287bc4eebccc8ec9742f2745 Gitweb: http://git.kernel.org/tip/54fd11fee59e7d05287bc4eebccc8ec9742f2745 Author: Peter Jones AuthorDate: Sat, 25 Jun 2016 08:20:25 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016

[tip:efi/core] efi: Document #define FOO_PROTOCOL_GUID layout

Commit-ID: 54fd11fee59e7d05287bc4eebccc8ec9742f2745 Gitweb: http://git.kernel.org/tip/54fd11fee59e7d05287bc4eebccc8ec9742f2745 Author: Peter Jones AuthorDate: Sat, 25 Jun 2016 08:20:25 +0100 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 13:06:55 +0200 efi: Document #define

[PATCH v3] staging: wilc1000: fix error handling in wilc_debugfs_init()

We can just ignore the return value from debugfs_create_dir() and debugfs_create_file(). The second one already interanlly checks the dentry created by the first before creating the file. debugfs was written so it would be easy to use, no need for error checking. Signed-off-by: Luis de

[PATCH v3] staging: wilc1000: fix error handling in wilc_debugfs_init()

We can just ignore the return value from debugfs_create_dir() and debugfs_create_file(). The second one already interanlly checks the dentry created by the first before creating the file. debugfs was written so it would be easy to use, no need for error checking. Signed-off-by: Luis de

[tip:sched/core] sched/core: Fix sched_getaffinity() return value kerneldoc comment

Commit-ID: 599b4840b0ea453c7d11e1798dcc8f494dcfd58a Gitweb: http://git.kernel.org/tip/599b4840b0ea453c7d11e1798dcc8f494dcfd58a Author: Zev Weiss AuthorDate: Sun, 26 Jun 2016 16:13:23 -0500 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016

[tip:x86/boot] x86/boot/64: Add forgotten end of function marker

Commit-ID: dbf984d825935f61965bcfacfd8e8dfdaf3e8051 Gitweb: http://git.kernel.org/tip/dbf984d825935f61965bcfacfd8e8dfdaf3e8051 Author: Borislav Petkov AuthorDate: Sat, 25 Jun 2016 13:24:57 +0200 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016

[tip:sched/core] sched/core: Fix sched_getaffinity() return value kerneldoc comment

Commit-ID: 599b4840b0ea453c7d11e1798dcc8f494dcfd58a Gitweb: http://git.kernel.org/tip/599b4840b0ea453c7d11e1798dcc8f494dcfd58a Author: Zev Weiss AuthorDate: Sun, 26 Jun 2016 16:13:23 -0500 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 12:53:12 +0200 sched/core: Fix

[tip:x86/boot] x86/boot/64: Add forgotten end of function marker

Commit-ID: dbf984d825935f61965bcfacfd8e8dfdaf3e8051 Gitweb: http://git.kernel.org/tip/dbf984d825935f61965bcfacfd8e8dfdaf3e8051 Author: Borislav Petkov AuthorDate: Sat, 25 Jun 2016 13:24:57 +0200 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 12:20:31 +0200 x86/boot/64: Add

Re: iommu/rockchip: Fix bugs and enable on ARM64

On Fri, Jun 24, 2016 at 10:13:25AM +0800, Shunqian Zheng wrote: > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 100 +++-- > drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 3 + > drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 221 > ++-- >

Re: iommu/rockchip: Fix bugs and enable on ARM64

On Fri, Jun 24, 2016 at 10:13:25AM +0800, Shunqian Zheng wrote: > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 100 +++-- > drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 3 + > drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 221 > ++-- >

[tip:locking/core] locking/qspinlock: Use __this_cpu_dec() instead of full-blown this_cpu_dec()

Commit-ID: 0dceeaf599e6d9b8bd908ba4bd3dfee84aa26be2 Gitweb: http://git.kernel.org/tip/0dceeaf599e6d9b8bd908ba4bd3dfee84aa26be2 Author: Pan Xinhui AuthorDate: Tue, 14 Jun 2016 14:37:27 +0800 Committer: Ingo Molnar CommitDate: Mon, 27 Jun

[tip:locking/core] locking/qspinlock: Use __this_cpu_dec() instead of full-blown this_cpu_dec()

Commit-ID: 0dceeaf599e6d9b8bd908ba4bd3dfee84aa26be2 Gitweb: http://git.kernel.org/tip/0dceeaf599e6d9b8bd908ba4bd3dfee84aa26be2 Author: Pan Xinhui AuthorDate: Tue, 14 Jun 2016 14:37:27 +0800 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 11:37:41 +0200 locking/qspinlock: Use

[tip:perf/core] perf/x86/intel: Add MSR_LAST_BRANCH_FROM_x quirk for ctx switch

Commit-ID: 71adae99ed187de9fcf988cc8873ee2c3af3385f Gitweb: http://git.kernel.org/tip/71adae99ed187de9fcf988cc8873ee2c3af3385f Author: David Carrillo-Cisneros AuthorDate: Tue, 21 Jun 2016 11:31:13 -0700 Committer: Ingo Molnar CommitDate: Mon, 27

[tip:perf/core] perf/x86/intel: Add MSR_LAST_BRANCH_FROM_x quirk for ctx switch

Commit-ID: 71adae99ed187de9fcf988cc8873ee2c3af3385f Gitweb: http://git.kernel.org/tip/71adae99ed187de9fcf988cc8873ee2c3af3385f Author: David Carrillo-Cisneros AuthorDate: Tue, 21 Jun 2016 11:31:13 -0700 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 11:34:20 +0200 perf/x86/intel:

[tip:perf/core] perf/x86/intel: Fix trivial formatting and style bug

Commit-ID: 3812bba84f3d721ff7dc3bb90360bc5ed6771994 Gitweb: http://git.kernel.org/tip/3812bba84f3d721ff7dc3bb90360bc5ed6771994 Author: David Carrillo-Cisneros AuthorDate: Tue, 21 Jun 2016 11:31:12 -0700 Committer: Ingo Molnar CommitDate: Mon, 27

[tip:perf/core] perf/x86/intel: Fix trivial formatting and style bug

Commit-ID: 3812bba84f3d721ff7dc3bb90360bc5ed6771994 Gitweb: http://git.kernel.org/tip/3812bba84f3d721ff7dc3bb90360bc5ed6771994 Author: David Carrillo-Cisneros AuthorDate: Tue, 21 Jun 2016 11:31:12 -0700 Committer: Ingo Molnar CommitDate: Mon, 27 Jun 2016 11:34:19 +0200 perf/x86/intel:

[tip:perf/core] perf/x86/intel: Fix MSR_LAST_BRANCH_FROM_x bug when no TSX

Commit-ID: 19fc9ddd61e059cc45464bdf6e8fa304bb94080f Gitweb: http://git.kernel.org/tip/19fc9ddd61e059cc45464bdf6e8fa304bb94080f Author: David Carrillo-Cisneros AuthorDate: Tue, 21 Jun 2016 11:31:11 -0700 Committer: Ingo Molnar CommitDate: Mon, 27

Re: [PATCH] fujitsu-laptop: Support touchpad toggle hotkey on Skylake-based models

> > Haswell-based Fujitsu laptops (Lifebook E734/E744/E754) have a touchpad > > toggle hotkey (Fn+F4) which is handled transparently to the operating > > system: while an ACPI notification is sent to FUJ02B1 when Fn+F4 is > > pressed, touchpad state is properly toggled without any explicit support

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