[PATCH v4 11/14] staging: comedi: daqboard2000: rename trigger control register macros

Rename the macros that define values for the trigger control register to avoid CamelCase, and to make it clearer which register they are associated with. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Shortened prefix from

[PATCH v4 10/14] staging: comedi: daqboard2000: redo DAC status macros and fix busy

Rename the macros defining values for the DAC status register to avoid CamelCase, and to make it clear which register they are associated with. Refactor the macros defining the regular DAC channel "busy" bits into a single macro that takes the DAC channel number as a parameter. Add a macro to

[PATCH v4 09/14] staging: comedi: daqboard2000: redo DAC control register macros

Rename the macros used to define values for the DAC control register to avoid CamelCase and to make it clearer which register they are associated with. Refactor the macros used to define values to enable or disable DAC channels to use the channel number as a parameter. None of these macros are

[PATCH v4 11/14] staging: comedi: daqboard2000: rename trigger control register macros

Rename the macros that define values for the trigger control register to avoid CamelCase, and to make it clearer which register they are associated with. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Shortened prefix from `DAQBOARD2000_` to `DB2K_`. v3, v4: No change. ---

[PATCH v4 01/14] staging: comedi: daqboard2000: remove commented out code

Remove some commented out code. Some of it uses constructs that don't exist in the driver, and probably come from the source code for the MS Windows driver. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Added comments to

[PATCH v4 00/14] staging: comedi: daqboard2000: checkpatch clean-ups

s series of patches to the daqboard2000 driver is mostly to fix the checkpatch.pl warnings. There is one warning remaining about one of the `udelay` calls with a parameter of 10 microseconds, but I decided to leave it alone, as converting it to `usleep_range` could increase firmware loading time.

[PATCH v4 03/14] staging: comedi: daqboard2000: CHECK: spaces preferred around that '*'

Fix checkpatch issues of the form "CHECK: spaces preferred around that '*' (ctx:VxV)". Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- CamelCase issues in this patch will be dealt with by later patches. v2, v3, v4: No change. ---

[PATCH v4 07/14] staging: comedi: daqboard2000: rename acquisition control register macros

Rename the macros defining values for the acquisition control register to avoid CamelCase, and to make it clearer which register they are associated with. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Shortened prefix from

[PATCH v4 13/14] staging: comedi: daqboard2000: rename CamelCase functions

Rename functions to avoid CamelCase warnings from checkpatch, and to use namespace associated with the driver. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Rebased due to v2 changes in previous patches. v3, v4: No change. ---

[PATCH v4 01/14] staging: comedi: daqboard2000: remove commented out code

Remove some commented out code. Some of it uses constructs that don't exist in the driver, and probably come from the source code for the MS Windows driver. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Added comments to offset and gain values that should be read from

[PATCH v4 00/14] staging: comedi: daqboard2000: checkpatch clean-ups

s series of patches to the daqboard2000 driver is mostly to fix the checkpatch.pl warnings. There is one warning remaining about one of the `udelay` calls with a parameter of 10 microseconds, but I decided to leave it alone, as converting it to `usleep_range` could increase firmware loading time.

[PATCH v4 03/14] staging: comedi: daqboard2000: CHECK: spaces preferred around that '*'

Fix checkpatch issues of the form "CHECK: spaces preferred around that '*' (ctx:VxV)". Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- CamelCase issues in this patch will be dealt with by later patches. v2, v3, v4: No change. --- drivers/staging/comedi/drivers/daqboard2000.c | 8

[PATCH v4 07/14] staging: comedi: daqboard2000: rename acquisition control register macros

Rename the macros defining values for the acquisition control register to avoid CamelCase, and to make it clearer which register they are associated with. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Shortened prefix from `DAQBOARD2000_` to `DB2K_`. v3: Rebased due to v3

[PATCH v4 13/14] staging: comedi: daqboard2000: rename CamelCase functions

Rename functions to avoid CamelCase warnings from checkpatch, and to use namespace associated with the driver. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- v2: Rebased due to v2 changes in previous patches. v3, v4: No change. --- drivers/staging/comedi/drivers/daqboard2000.c |

Re: [PATCH v12 07/13] task_isolation: add debug boot flag

On 5/19/2016 1:54 PM, Peter Zijlstra wrote: So the 'simple' thing is: struct rq *rq = cpu_rq(cpu); struct task_struct *task; raw_spin_lock_irq(>lock); task = rq->curr; get_task_struct(task); raw_spin_unlock_irq(>lock); Because by holding

Re: [PATCH v12 07/13] task_isolation: add debug boot flag

On 5/19/2016 1:54 PM, Peter Zijlstra wrote: So the 'simple' thing is: struct rq *rq = cpu_rq(cpu); struct task_struct *task; raw_spin_lock_irq(>lock); task = rq->curr; get_task_struct(task); raw_spin_unlock_irq(>lock); Because by holding

Re: [PATCH v2 00/14] staging: comedi: daqboard2000: checkpatch clean-ups

On 19/05/16 11:16, Ian Abbott wrote: On 19/05/16 11:02, Ian Abbott wrote: On 18/05/16 13:36, Ian Abbott wrote: Patches 03 and 06 have checkpatch warnings themselves about CamelCase issues, but they are not "new" issues, and are resolved by the later patches in the series. 01) staging: comedi:

Re: [PATCH v2 00/14] staging: comedi: daqboard2000: checkpatch clean-ups

On 19/05/16 11:16, Ian Abbott wrote: On 19/05/16 11:02, Ian Abbott wrote: On 18/05/16 13:36, Ian Abbott wrote: Patches 03 and 06 have checkpatch warnings themselves about CamelCase issues, but they are not "new" issues, and are resolved by the later patches in the series. 01) staging: comedi:

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On Thu, May 19, 2016 at 6:27 AM, Wanpeng Li wrote: > From: Wanpeng Li > > If an emulated lapic timer will fire soon(in the scope of 10us the > base of dynamic halt-polling, lower-end of message passing workload > latency TCP_RR's poll time < 10us) we

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On Thu, May 19, 2016 at 6:27 AM, Wanpeng Li wrote: > From: Wanpeng Li > > If an emulated lapic timer will fire soon(in the scope of 10us the > base of dynamic halt-polling, lower-end of message passing workload > latency TCP_RR's poll time < 10us) we can treat it as a short halt, > and poll to

[GIT PULL] localmodconfig: Updates and clean ups for streamline-config.pl

Linus, Benjamin Poirier added some minor fixes and clean ups to localmodconfig. One is a fix for making sure that module signing still works when coming from a different environment. If original keys are not found, it will warn and reset the keys to their default value. Please pull the latest

[GIT PULL] localmodconfig: Updates and clean ups for streamline-config.pl

Linus, Benjamin Poirier added some minor fixes and clean ups to localmodconfig. One is a fix for making sure that module signing still works when coming from a different environment. If original keys are not found, it will warn and reset the keys to their default value. Please pull the latest

[PATCH] scsi: ultrastor.c depends on ISA_DMA_API

Werror=implicit-function-declaration] free_dma(shost->dma_channel); ^ Signed-off-by: Randy Dunlap <rdun...@infradead.org> --- drivers/scsi/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Found in linux-next but also applies to mainline. --- linux-next-20160519.orig/dr

[PATCH] scsi: ultrastor.c depends on ISA_DMA_API

free_dma(shost->dma_channel); ^ Signed-off-by: Randy Dunlap --- drivers/scsi/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Found in linux-next but also applies to mainline. --- linux-next-20160519.orig/drivers/scsi/Kconfig +++ linux-next-20160519/drivers/scsi/Kconf

[RFC] iio: add driver for si114x ambient light / proximity sensors

The si114x supports x=1,2,3 IR LEDs for proximity sensing together with visible and IR ambient light sensing (ALS) Arranging 3 IR LEDs in a triangular shape can be used for detection of swipe gestures (the present driver only measures the intensities, it does not process the data). There is an

[RFC] iio: add driver for si114x ambient light / proximity sensors

The si114x supports x=1,2,3 IR LEDs for proximity sensing together with visible and IR ambient light sensing (ALS) Arranging 3 IR LEDs in a triangular shape can be used for detection of swipe gestures (the present driver only measures the intensities, it does not process the data). There is an

Re: [PATCH v12 07/13] task_isolation: add debug boot flag

On Thu, May 19, 2016 at 10:42:39AM -0400, Chris Metcalf wrote: > + rcu_read_lock(); > + p = cpu_curr(cpu); Here @cpu can schedule, hit TASK_DEAD and do put_task_struct() and kfree() the task. > + get_task_struct(p); And here we then do a use-after-free. > + rcu_read_unlock();

Re: [PATCH v12 07/13] task_isolation: add debug boot flag

On Thu, May 19, 2016 at 10:42:39AM -0400, Chris Metcalf wrote: > + rcu_read_lock(); > + p = cpu_curr(cpu); Here @cpu can schedule, hit TASK_DEAD and do put_task_struct() and kfree() the task. > + get_task_struct(p); And here we then do a use-after-free. > + rcu_read_unlock();

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

Hello Heikki, On Thu, May 19, 2016 at 03:44:54PM +0300, Heikki Krogerus wrote: > The purpose of this class is to provide unified interface for user > space to get the status and basic information about USB Type-C > Connectors in the system, control data role swapping, and when USB PD > is

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

Hello Heikki, On Thu, May 19, 2016 at 03:44:54PM +0300, Heikki Krogerus wrote: > The purpose of this class is to provide unified interface for user > space to get the status and basic information about USB Type-C > Connectors in the system, control data role swapping, and when USB PD > is

[ANNOUNCE] Git v2.8.3

The latest maintenance release Git v2.8.3 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.8.3' tag and the 'maint' branch that the tag points at: url =

[ANNOUNCE] Git v2.8.3

The latest maintenance release Git v2.8.3 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.8.3' tag and the 'maint' branch that the tag points at: url =

[PATCH] f2fs: introduce on-disk layout version checking functionality

From: Vyacheslav Dubeyko Date: Wed, 18 May 2016 15:58:00 -0700 Subject: [PATCH] f2fs: introduce on-disk layout version checking functionality Currently, F2FS has 16TB limitation on volume size. But 16TB NAND-based SSDs are around the corner. Unfortunately, support of

[PATCH] f2fs: introduce on-disk layout version checking functionality

From: Vyacheslav Dubeyko Date: Wed, 18 May 2016 15:58:00 -0700 Subject: [PATCH] f2fs: introduce on-disk layout version checking functionality Currently, F2FS has 16TB limitation on volume size. But 16TB NAND-based SSDs are around the corner. Unfortunately, support of 16TB+ volume size needs in

Re: [PATCH] mm: compact: fix zoneindex in compact

On 19.5.2016 19:23, Hugh Dickins wrote: > On Thu, 19 May 2016, Vlastimil Babka wrote: >> On 05/19/2016 02:11 PM, Vlastimil Babka wrote: >>> On 05/19/2016 01:58 PM, Chen Feng wrote: While testing the kcompactd in my platform 3G MEM only DMA ZONE. I found the kcompactd never wakeup. It

Re: [PATCH] mm: compact: fix zoneindex in compact

On 19.5.2016 19:23, Hugh Dickins wrote: > On Thu, 19 May 2016, Vlastimil Babka wrote: >> On 05/19/2016 02:11 PM, Vlastimil Babka wrote: >>> On 05/19/2016 01:58 PM, Chen Feng wrote: While testing the kcompactd in my platform 3G MEM only DMA ZONE. I found the kcompactd never wakeup. It

Re: [PATCH v3 06/14] staging: comedi: daqboard2000: rename register offset macros

On 19/05/16 17:49, Hartley Sweeten wrote: On Thursday, May 19, 2016 2:56 AM, Ian Abbott wrote: Rename the macros defining register offsets to avoid CamelCase, and to use namespace associated with the driver. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten

Re: [PATCH v3 06/14] staging: comedi: daqboard2000: rename register offset macros

On 19/05/16 17:49, Hartley Sweeten wrote: On Thursday, May 19, 2016 2:56 AM, Ian Abbott wrote: Rename the macros defining register offsets to avoid CamelCase, and to use namespace associated with the driver. Signed-off-by: Ian Abbott Reviewed-by: H Hartley Sweeten --- Other CamelCase issues

Re: linux-next: build failure after merge of the nfs tree

On 05/19/2016 08:06 AM, Trond Myklebust wrote: > Thanks Stephen! > > Anna will be managing pushing the NFS client changes to Linus during > this merge window, so I'm assuming she will include this and your > other fixup in her pull request. Yep! I'll make sure it's in there. Anna > > Cheers

Re: linux-next: build failure after merge of the nfs tree

On 05/19/2016 08:06 AM, Trond Myklebust wrote: > Thanks Stephen! > > Anna will be managing pushing the NFS client changes to Linus during > this merge window, so I'm assuming she will include this and your > other fixup in her pull request. Yep! I'll make sure it's in there. Anna > > Cheers

Re: [Intel-gfx] [PATCH 3/3] Introduce & use new lightweight SGL iterators

On Tue, May 17, 2016 at 01:05:48PM +0100, Dave Gordon wrote: > On 17/05/16 11:34, Tvrtko Ursulin wrote: > > > >On 16/05/16 16:19, Dave Gordon wrote: > >>The existing for_each_sg_page() iterator is somewhat heavyweight, and is > >>limiting i915 driver performance in a few benchmarks. So here we >

Re: [Intel-gfx] [PATCH 3/3] Introduce & use new lightweight SGL iterators

On Tue, May 17, 2016 at 01:05:48PM +0100, Dave Gordon wrote: > On 17/05/16 11:34, Tvrtko Ursulin wrote: > > > >On 16/05/16 16:19, Dave Gordon wrote: > >>The existing for_each_sg_page() iterator is somewhat heavyweight, and is > >>limiting i915 driver performance in a few benchmarks. So here we >

Re: [PATCH] mm: compact: fix zoneindex in compact

On Thu, 19 May 2016, Vlastimil Babka wrote: > On 05/19/2016 02:11 PM, Vlastimil Babka wrote: > > On 05/19/2016 01:58 PM, Chen Feng wrote: > >> While testing the kcompactd in my platform 3G MEM only DMA ZONE. > >> I found the kcompactd never wakeup. It seems the zoneindex > >> has already minus 1

Re: [PATCH] mm: compact: fix zoneindex in compact

On Thu, 19 May 2016, Vlastimil Babka wrote: > On 05/19/2016 02:11 PM, Vlastimil Babka wrote: > > On 05/19/2016 01:58 PM, Chen Feng wrote: > >> While testing the kcompactd in my platform 3G MEM only DMA ZONE. > >> I found the kcompactd never wakeup. It seems the zoneindex > >> has already minus 1

[PATCH] dma-debug: Avoid spinlock recursion when disabling dma-debug

From: Ville Syrjälä With netconsole (at least) the pr_err("... disabling\n") call can recurse back into the dma-debug code, where it'll try to grab free_entries_lock again. Avoid the problem by doing the printk after dropping the lock. Cc: sta...@vger.kernel.org

[PATCH] dma-debug: Avoid spinlock recursion when disabling dma-debug

From: Ville Syrjälä With netconsole (at least) the pr_err("... disabling\n") call can recurse back into the dma-debug code, where it'll try to grab free_entries_lock again. Avoid the problem by doing the printk after dropping the lock. Cc: sta...@vger.kernel.org Cc: Andrew Morton

Re: [PATCH] arm64: defconfig: Enable cros-ec and battery driver

On 5/3/2016 11:45 AM, Rhyland Klein wrote: > Enable the ChromeOS Embedded Controller, its I2C tunnel driver, and > the BA27XXX battery driver. These are all used on the Tegra210 Smaug > platform. > > Signed-off-by: Rhyland Klein Has anyone had a chance to review this yet?

Re: [PATCH] arm64: defconfig: Enable cros-ec and battery driver

On 5/3/2016 11:45 AM, Rhyland Klein wrote: > Enable the ChromeOS Embedded Controller, its I2C tunnel driver, and > the BA27XXX battery driver. These are all used on the Tegra210 Smaug > platform. > > Signed-off-by: Rhyland Klein Has anyone had a chance to review this yet? -rhyland > --- >

Re: [PATCH] mm: page_is_guard return false when page_ext arrays are not allocated yet

On 5/18/2016 5:28 PM, Joonsoo Kim wrote: Vlastiml, thanks for ccing me on original bug report. On Wed, May 18, 2016 at 03:23:45PM -0700, Yang Shi wrote: When enabling the below kernel configs: CONFIG_DEFERRED_STRUCT_PAGE_INIT CONFIG_DEBUG_PAGEALLOC CONFIG_PAGE_EXTENSION CONFIG_DEBUG_VM

Re: [PATCH] mm: page_is_guard return false when page_ext arrays are not allocated yet

On 5/18/2016 5:28 PM, Joonsoo Kim wrote: Vlastiml, thanks for ccing me on original bug report. On Wed, May 18, 2016 at 03:23:45PM -0700, Yang Shi wrote: When enabling the below kernel configs: CONFIG_DEFERRED_STRUCT_PAGE_INIT CONFIG_DEBUG_PAGEALLOC CONFIG_PAGE_EXTENSION CONFIG_DEBUG_VM

Re: [PATCH v3] xen: add steal_clock support on x86

On Thu, 19 May 2016, Stefano Stabellini wrote: > On Thu, 19 May 2016, Juergen Gross wrote: > > The pv_time_ops structure contains a function pointer for the > > "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86 > > uses its own mechanism to account for the "stolen" time a

Re: [PATCH v3] xen: add steal_clock support on x86

On Thu, 19 May 2016, Stefano Stabellini wrote: > On Thu, 19 May 2016, Juergen Gross wrote: > > The pv_time_ops structure contains a function pointer for the > > "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86 > > uses its own mechanism to account for the "stolen" time a

Re: ioatdma(Intel(R) I/OAT DMA Engine init failed)

On Thu, May 19, 2016 at 08:19:30PM +0530, Jiang, Dave wrote: > > -Original Message- > > From: Gavin Guo [mailto:gavin@canonical.com] > > Sent: Wednesday, May 18, 2016 8:19 PM > > To: Jiang, Dave > > Cc: Koul, Vinod ;

Re: ioatdma(Intel(R) I/OAT DMA Engine init failed)

On Thu, May 19, 2016 at 08:19:30PM +0530, Jiang, Dave wrote: > > -Original Message- > > From: Gavin Guo [mailto:gavin@canonical.com] > > Sent: Wednesday, May 18, 2016 8:19 PM > > To: Jiang, Dave > > Cc: Koul, Vinod ; dmaeng...@vger.kernel.org; > > linux-kernel@vger.kernel.org;

Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind

On Thu, May 19, 2016 at 06:46:09PM +0200, Jiri Olsa wrote: > On Thu, May 19, 2016 at 11:47:38AM +, He Kuang wrote: > > SNIP > > > #endif /* ARCH_PERF_COMMON_H */ > > diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile > > index 1e46277..a86b864 100644 > > ---

Re: [PATCH v3] xen: add steal_clock support on x86

On Thu, 19 May 2016, Juergen Gross wrote: > The pv_time_ops structure contains a function pointer for the > "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86 > uses its own mechanism to account for the "stolen" time a thread wasn't > able to run due to hypervisor scheduling.

Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind

On Thu, May 19, 2016 at 06:46:09PM +0200, Jiri Olsa wrote: > On Thu, May 19, 2016 at 11:47:38AM +, He Kuang wrote: > > SNIP > > > #endif /* ARCH_PERF_COMMON_H */ > > diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile > > index 1e46277..a86b864 100644 > > ---

Re: [PATCH v3] xen: add steal_clock support on x86

On Thu, 19 May 2016, Juergen Gross wrote: > The pv_time_ops structure contains a function pointer for the > "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86 > uses its own mechanism to account for the "stolen" time a thread wasn't > able to run due to hypervisor scheduling.

Re: [PATCH] PM / sleep: fix unbalanced pm runtime disable in __device_suspend_late()

On 05/19/2016 04:38 PM, Rafael J. Wysocki wrote: > On Fri, May 13, 2016 at 8:03 PM, Grygorii Strashko > wrote: >> The PM runtime will be left disabled for the device if its .suspend_late() >> callback fails and async suspend is not allowed for this device. In >> this

Re: [PATCH] PM / sleep: fix unbalanced pm runtime disable in __device_suspend_late()

On 05/19/2016 04:38 PM, Rafael J. Wysocki wrote: > On Fri, May 13, 2016 at 8:03 PM, Grygorii Strashko > wrote: >> The PM runtime will be left disabled for the device if its .suspend_late() >> callback fails and async suspend is not allowed for this device. In >> this case device will not be added

[PATCH 3/7] pref annotate: Separate architecture specific annotation support

Currently the list of instructions recognised by perf annotate contains an intermingled mix of x86 and ARM instructions, and the x86 instructions are unconditionally included on all platforms. This means that perf attempts to parse x86 instructions on non-x86 platforms. Refactor the instruction

[PATCH 3/7] pref annotate: Separate architecture specific annotation support

Currently the list of instructions recognised by perf annotate contains an intermingled mix of x86 and ARM instructions, and the x86 instructions are unconditionally included on all platforms. This means that perf attempts to parse x86 instructions on non-x86 platforms. Refactor the instruction

[PATCH 1/7] perf annotate: Fix identification of ARM blt and bls instructions

The ARM blt and bls instructions are not correctly identified when parsing assembly because the list of recognised instructions must be sorted by name. Swap the ordering of blt and bls. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra

[PATCH 6/7] perf annotate: Make action message be architecture specific

The help message displayed by perf report when pressing right arrow or enter keys on an instruction that doesn't have an action is currently hard coded and displays x86 instructions regardless of the target architecture. Make the help message architecture specific. Signed-off-by: Chris Ryder

[PATCH 1/7] perf annotate: Fix identification of ARM blt and bls instructions

The ARM blt and bls instructions are not correctly identified when parsing assembly because the list of recognised instructions must be sorted by name. Swap the ordering of blt and bls. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Arnaldo Carvalho de

[PATCH 6/7] perf annotate: Make action message be architecture specific

The help message displayed by perf report when pressing right arrow or enter keys on an instruction that doesn't have an action is currently hard coded and displays x86 instructions regardless of the target architecture. Make the help message architecture specific. Signed-off-by: Chris Ryder

[PATCH 7/7] perf annotate: AArch64 support

Add basic support to recognise AArch64 assembly. This allows perf to identify AArch64 instructions that branch to other parts within the same function, thereby properly annotating them. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra

[PATCH 5/7] perf annotate: Architecture neutral handling of return instruction

Currently perf annotate is hard coded to look for the x86 'retq' instruction when annotating disassembly, regardless of the target architecture. Move architecture specific processing of return instructions into per-architecture header files. Signed-off-by: Chris Ryder

[PATCH 4/7] perf annotate: Separate out architecture specific parsing

Currently call__parse and mov__parse contain #ifdefs for ARM specific parsing. Move the architecture specific parsing into the per-architecture annotate_ins.h files. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra

[PATCH 0/7] perf annotate: Support for AArch64

Hi, The linux perf tool has some basic support for annotating AArch32 branch instructions when displaying assembly. This patchset refactors the annotation support to have a cleaner separation between architectures, and then adds support for annotating AArch64 instructions. Comments very welcome,

[PATCH 7/7] perf annotate: AArch64 support

Add basic support to recognise AArch64 assembly. This allows perf to identify AArch64 instructions that branch to other parts within the same function, thereby properly annotating them. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Arnaldo Carvalho de

[PATCH 5/7] perf annotate: Architecture neutral handling of return instruction

Currently perf annotate is hard coded to look for the x86 'retq' instruction when annotating disassembly, regardless of the target architecture. Move architecture specific processing of return instructions into per-architecture header files. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc:

[PATCH 4/7] perf annotate: Separate out architecture specific parsing

Currently call__parse and mov__parse contain #ifdefs for ARM specific parsing. Move the architecture specific parsing into the per-architecture annotate_ins.h files. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Arnaldo Carvalho de Melo Cc: Alexander

[PATCH 0/7] perf annotate: Support for AArch64

Hi, The linux perf tool has some basic support for annotating AArch32 branch instructions when displaying assembly. This patchset refactors the annotation support to have a cleaner separation between architectures, and then adds support for annotating AArch64 instructions. Comments very welcome,

[PATCH 2/7] perf annotate: Sort list of recognised instructions

Currently the list of instructions recognised by perf annotate has to be explicitly written in sorted order. This makes it easy to make mistakes when adding new instructions. Sort the list of instructions on first access. Signed-off-by: Chris Ryder Acked-by: Pawel Moll

[PATCH 2/7] perf annotate: Sort list of recognised instructions

Currently the list of instructions recognised by perf annotate has to be explicitly written in sorted order. This makes it easy to make mistakes when adding new instructions. Sort the list of instructions on first access. Signed-off-by: Chris Ryder Acked-by: Pawel Moll Cc: Peter Zijlstra Cc:

Re: [PATCH v3] Force cppc_cpufreq to report values in KHz to fix user space reporting

On 05/19/2016 07:12 AM, Rafael J. Wysocki wrote: > On Thu, May 19, 2016 at 1:41 AM, Al Stone wrote: >> When CPPC is being used by ACPI on arm64, user space tools such as >> cpupower report CPU frequency values from sysfs that are incorrect. >> >> What the driver was doing was

Re: [PATCH v3] Force cppc_cpufreq to report values in KHz to fix user space reporting

On 05/19/2016 07:12 AM, Rafael J. Wysocki wrote: > On Thu, May 19, 2016 at 1:41 AM, Al Stone wrote: >> When CPPC is being used by ACPI on arm64, user space tools such as >> cpupower report CPU frequency values from sysfs that are incorrect. >> >> What the driver was doing was reporting the values

Re: get_maintainer.pl and MAINTAINERS file

Em Thu, 19 May 2016 16:25:45 +0200 Richard Weinberger escreveu: > On Thu, May 19, 2016 at 2:57 PM, Kalle Valo wrote: > > (Changed the subject from "Re: [PATCH v6 0/3] auxdisplay: Introduce ht16k33 > > driver") > > > > Robin van der Gracht

Re: get_maintainer.pl and MAINTAINERS file

Em Thu, 19 May 2016 16:25:45 +0200 Richard Weinberger escreveu: > On Thu, May 19, 2016 at 2:57 PM, Kalle Valo wrote: > > (Changed the subject from "Re: [PATCH v6 0/3] auxdisplay: Introduce ht16k33 > > driver") > > > > Robin van der Gracht writes: > > > >>> And 4th, what is with the insane

Re: [PATCH V7 08/11] pci, acpi: Support for ACPI based generic PCI host controller

On 10/05/16 17:19, Tomasz Nowicki wrote: This patch is going to implement generic PCI host controller for ACPI world, similar to what pci-host-generic.c driver does for DT world. All such drivers, which we have seen so far, were implemented within arch/ directory since they had some arch

Re: [PATCH V7 08/11] pci, acpi: Support for ACPI based generic PCI host controller

On 10/05/16 17:19, Tomasz Nowicki wrote: This patch is going to implement generic PCI host controller for ACPI world, similar to what pci-host-generic.c driver does for DT world. All such drivers, which we have seen so far, were implemented within arch/ directory since they had some arch

Re: [PATCH v3] mmc: dw_mmc: rockchip: Set the drive phase properly

2016-05-13 0:52 GMT+02:00 Heiko Stuebner : > Am Donnerstag, 12. Mai 2016, 11:31:50 schrieb Douglas Anderson: > > [...] > >> In commit 7a03fe6f48f3 ("clk: rockchip: reset init state before mmc card >> initialization") we actually started setting this explicitly in the >> kernel,

Re: [PATCH v3] mmc: dw_mmc: rockchip: Set the drive phase properly

2016-05-13 0:52 GMT+02:00 Heiko Stuebner : > Am Donnerstag, 12. Mai 2016, 11:31:50 schrieb Douglas Anderson: > > [...] > >> In commit 7a03fe6f48f3 ("clk: rockchip: reset init state before mmc card >> initialization") we actually started setting this explicitly in the >> kernel, but that commit

[PATCH] ACPI / tables: Return error from table parse handler

The handler called in acpi_table_parse may return an error. This patch returns this error instead of ignoring it. Signed-off-by: Matthias Brugger --- drivers/acpi/tables.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/acpi/tables.c

[PATCH] ACPI / tables: Return error from table parse handler

The handler called in acpi_table_parse may return an error. This patch returns this error instead of ignoring it. Signed-off-by: Matthias Brugger --- drivers/acpi/tables.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c

Re: [GIT PULL] ARC updates for 4.7-rc1

On Wed, May 18, 2016 at 11:24 PM, Vineet Gupta wrote: > Hi Linus, > > We have a relatively big changeset for ARC for 4.7. .. this pull request is missing the diffstat, though, so it's hard to see that your "big changeset" matches what I actually get. To make matters

Re: [GIT PULL] ARC updates for 4.7-rc1

On Wed, May 18, 2016 at 11:24 PM, Vineet Gupta wrote: > Hi Linus, > > We have a relatively big changeset for ARC for 4.7. .. this pull request is missing the diffstat, though, so it's hard to see that your "big changeset" matches what I actually get. To make matters worse, the shortlog doesn't

RE: [PATCH v3 06/14] staging: comedi: daqboard2000: rename register offset macros

On Thursday, May 19, 2016 2:56 AM, Ian Abbott wrote: > Rename the macros defining register offsets to avoid CamelCase, and to > use namespace associated with the driver. > > Signed-off-by: Ian Abbott > Reviewed-by: H Hartley Sweeten > --- > Other

RE: [PATCH v3 06/14] staging: comedi: daqboard2000: rename register offset macros

On Thursday, May 19, 2016 2:56 AM, Ian Abbott wrote: > Rename the macros defining register offsets to avoid CamelCase, and to > use namespace associated with the driver. > > Signed-off-by: Ian Abbott > Reviewed-by: H Hartley Sweeten > --- > Other CamelCase issues in this patch will be dealt with

Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind

On Thu, May 19, 2016 at 11:47:38AM +, He Kuang wrote: SNIP > #endif /* ARCH_PERF_COMMON_H */ > diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile > index 1e46277..a86b864 100644 > --- a/tools/perf/config/Makefile > +++ b/tools/perf/config/Makefile > @@ -345,6 +345,12 @@

Re: [PATCH v4 2/6] perf tools: Promote proper messages for cross-platform unwind

On Thu, May 19, 2016 at 11:47:38AM +, He Kuang wrote: SNIP > #endif /* ARCH_PERF_COMMON_H */ > diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile > index 1e46277..a86b864 100644 > --- a/tools/perf/config/Makefile > +++ b/tools/perf/config/Makefile > @@ -345,6 +345,12 @@

[PATCH] f2fs: flush pending bios right away when error occurs

Given errors, this patch flushes pending bios as soon as possible. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 +++ fs/f2fs/f2fs.h | 7 +-- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c

[PATCH] f2fs: flush pending bios right away when error occurs

Given errors, this patch flushes pending bios as soon as possible. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 7 +++ fs/f2fs/f2fs.h | 7 +-- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c index cf79598..ecf7153

Re: [PATCH] rtc: interface: ignore exprired timers one enqueing new timers

Hi Colin, On 16/05/2016 at 17:22:54 +0100, Colin King wrote : > From: Colin Ian King > > This patch fixes a RTC wakealarm issue, namely, the event fires during > hibernate and is not cleared from the list, causing hwclock to block. > > The current enqueuing does not

Re: [PATCH] rtc: interface: ignore exprired timers one enqueing new timers

Hi Colin, On 16/05/2016 at 17:22:54 +0100, Colin King wrote : > From: Colin Ian King > > This patch fixes a RTC wakealarm issue, namely, the event fires during > hibernate and is not cleared from the list, causing hwclock to block. > > The current enqueuing does not trigger an alarm if any

Re: [PATCH 1/2] Input: migor-ts - allow driver to build if COMPILE_TEST is enabled

On Tue, May 17, 2016 at 12:32:37PM -0400, Javier Martinez Canillas wrote: > The driver only has runtime but no build time dependency with SH_MIGOR, so > it can be built for testing purposes if the COMPILE_TEST option is enabled. > > This is useful to have more build coverage and make sure that

Re: [PATCH 2/2] Input: migor-ts - fix error for modular build

On Tue, May 17, 2016 at 12:32:38PM -0400, Javier Martinez Canillas wrote: > There is a typo in the driver for the I2C device table that is passed to > the MODULE_DEVICE_TABLE() macro, this leads to the following build error: > > CC [M] drivers/input/touchscreen//migor_ts.o >

Re: [PATCH 1/2] Input: migor-ts - allow driver to build if COMPILE_TEST is enabled

On Tue, May 17, 2016 at 12:32:37PM -0400, Javier Martinez Canillas wrote: > The driver only has runtime but no build time dependency with SH_MIGOR, so > it can be built for testing purposes if the COMPILE_TEST option is enabled. > > This is useful to have more build coverage and make sure that

Re: [PATCH 2/2] Input: migor-ts - fix error for modular build

On Tue, May 17, 2016 at 12:32:38PM -0400, Javier Martinez Canillas wrote: > There is a typo in the driver for the I2C device table that is passed to > the MODULE_DEVICE_TABLE() macro, this leads to the following build error: > > CC [M] drivers/input/touchscreen//migor_ts.o >

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