Re: [PATCH v5 02/12] x86/apic: Prepare for unifying the interrupt delivery modes setup

Hi Thomas, At 07/03/2017 01:47 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: +/* Init the interrupt delivery mode for the BSP */ +void __init apic_intr_mode_init(void) +{ + switch (apic_intr_mode_select()) { + case APIC_PIC: +

Re: [PATCH v5 02/12] x86/apic: Prepare for unifying the interrupt delivery modes setup

Hi Thomas, At 07/03/2017 01:47 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: +/* Init the interrupt delivery mode for the BSP */ +void __init apic_intr_mode_init(void) +{ + switch (apic_intr_mode_select()) { + case APIC_PIC: +

Re: linux-next: manual merge of the kvms390 tree with the s390 tree

Hi all, [cc'ing kvm tree maintainers] Withe the merge window opening, just a reminder that this conflict still exists. On Thu, 22 Jun 2017 12:59:28 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the kvms390 tree got a conflict in: > >

Re: [PATCH v4] PCI: Workaround wrong flags completions for IDT switch

James, On Wed, Jun 28, 2017 at 5:42 AM, James Puthukattukaran wrote: > From: James Puthukattukaran > > The IDT switch incorrectly flags an ACS source violation on a read config > request to an end point device on the completion

Re: linux-next: manual merge of the kvms390 tree with the s390 tree

Hi all, [cc'ing kvm tree maintainers] Withe the merge window opening, just a reminder that this conflict still exists. On Thu, 22 Jun 2017 12:59:28 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the kvms390 tree got a conflict in: > > arch/s390/kvm/gaccess.c > > between

Re: [PATCH v4] PCI: Workaround wrong flags completions for IDT switch

James, On Wed, Jun 28, 2017 at 5:42 AM, James Puthukattukaran wrote: > From: James Puthukattukaran > > The IDT switch incorrectly flags an ACS source violation on a read config > request to an end point device on the completion (IDT 89H32H8G3-YC, > errata #36) even though the PCI Express spec

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

Hi all, With the merge window opening, just a reminder that this merge fixup is still required. On Thu, 22 Jun 2017 11:44:56 +1000 Stephen Rothwell wrote: > > After merging the md tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > >

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

Hi all, With the merge window opening, just a reminder that this merge fixup is still required. On Thu, 22 Jun 2017 11:44:56 +1000 Stephen Rothwell wrote: > > After merging the md tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/md/md.c: In function

Re: linux-next: manual merge of the net-next tree with the pci tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 21 Jun 2017 11:54:43 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the net-next tree got a conflict in: > > drivers/net/wireless/marvell/mwifiex/pcie.c > >

Re: linux-next: manual merge of the net-next tree with the pci tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 21 Jun 2017 11:54:43 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the net-next tree got a conflict in: > > drivers/net/wireless/marvell/mwifiex/pcie.c > > between commit: > >

Re: linux-next: manual merge of the kspp tree with the file-locks tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 21 Jun 2017 16:32:11 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the kspp tree got a conflict in: > > include/linux/fs.h > > between commits: > >

Re: linux-next: manual merge of the kspp tree with the file-locks tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 21 Jun 2017 16:32:11 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the kspp tree got a conflict in: > > include/linux/fs.h > > between commits: > > 7356fd927059 ("fs: new

Re: [PATCH v5 01/12] x86/apic: Construct a selector for the interrupt delivery mode

Hi Thomas, At 07/03/2017 01:37 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: +static int __init apic_intr_mode_select(void) +{ + /* Check kernel option */ + if (disable_apic) { + pr_info("APIC disabled via kernel command line\n"); +

Re: [PATCH v5 01/12] x86/apic: Construct a selector for the interrupt delivery mode

Hi Thomas, At 07/03/2017 01:37 AM, Thomas Gleixner wrote: On Fri, 30 Jun 2017, Dou Liyang wrote: +static int __init apic_intr_mode_select(void) +{ + /* Check kernel option */ + if (disable_apic) { + pr_info("APIC disabled via kernel command line\n"); +

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got conflicts in: drivers/net/ethernet/mellanox/mlx5/core/health.c include/linux/mlx5/driver.h between commit: 2a0165a034ac ("net/mlx5: Cancel delayed recovery work when unloading the driver") from the net tree and commit:

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got conflicts in: drivers/net/ethernet/mellanox/mlx5/core/health.c include/linux/mlx5/driver.h between commit: 2a0165a034ac ("net/mlx5: Cancel delayed recovery work when unloading the driver") from the net tree and commit:

linux-next: manual merge of the net-next tree with the arm64 tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: arch/arm64/net/bpf_jit_comp.c between commit: 425e1ed73e65 ("arm64: fix endianness annotation for 'struct jit_ctx' and friends") from the arm64 tree and commit: f1c9eed7f437 ("bpf, arm64: take advantage of

linux-next: manual merge of the net-next tree with the arm64 tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: arch/arm64/net/bpf_jit_comp.c between commit: 425e1ed73e65 ("arm64: fix endianness annotation for 'struct jit_ctx' and friends") from the arm64 tree and commit: f1c9eed7f437 ("bpf, arm64: take advantage of

Re: linux-next: manual merge of the tip tree with the jc_docs tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 21 Jun 2017 14:18:09 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > Documentation/DocBook/kernel-hacking.tmpl > >

Re: linux-next: manual merge of the tip tree with the jc_docs tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 21 Jun 2017 14:18:09 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > Documentation/DocBook/kernel-hacking.tmpl > > between commit: > >

Re: linux-next: manual merge of the akpm-current tree with the kspp tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Tue, 20 Jun 2017 15:15:49 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > > include/linux/sem.h > > between commit: >

Re: linux-next: manual merge of the akpm-current tree with the kspp tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Tue, 20 Jun 2017 15:15:49 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > > include/linux/sem.h > > between commit: > > 1a12979f61e4

Re: linux-next: manual merge of the tty tree with the arm-soc tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Tue, 20 Jun 2017 13:52:42 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tty tree got a conflict in: > > include/linux/platform_data/atmel.h > > between

Re: linux-next: manual merge of the tty tree with the arm-soc tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Tue, 20 Jun 2017 13:52:42 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tty tree got a conflict in: > > include/linux/platform_data/atmel.h > > between commit: > > 8a3d809373c6

Re: linux-next: manual merge of the tip tree with the arm64 tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Fri, 16 Jun 2017 13:25:03 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > drivers/acpi/apei/ghes.c > > between commit: > >

Re: linux-next: manual merge of the tip tree with the arm64 tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Fri, 16 Jun 2017 13:25:03 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > drivers/acpi/apei/ghes.c > > between commit: > > d0189b2eef2e ("acpi:

Re: [PATCH v2] zswap: Zero-filled pages handling

On Sun, Jul 2, 2017 at 9:19 AM, Srividya Desireddy wrote: > From: Srividya Desireddy > Date: Sun, 2 Jul 2017 19:15:37 +0530 > Subject: [PATCH v2] zswap: Zero-filled pages handling > > Zswap is a cache which compresses the pages that are being

Re: [PATCH v2] zswap: Zero-filled pages handling

On Sun, Jul 2, 2017 at 9:19 AM, Srividya Desireddy wrote: > From: Srividya Desireddy > Date: Sun, 2 Jul 2017 19:15:37 +0530 > Subject: [PATCH v2] zswap: Zero-filled pages handling > > Zswap is a cache which compresses the pages that are being swapped out > and stores them into a dynamically

[PATCH] staging: sm750fb: skip unnecessary comparisons

introduced early checks to skip unnecessary comparisons when flags set. Signed-off-by: Lynn Lei --- drivers/staging/sm750fb/sm750.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/drivers/staging/sm750fb/sm750.c

Re: linux-next: manual merge of the char-misc tree with the jc_docs tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 14 Jun 2017 14:04:16 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the char-misc tree got a conflict in: > > Documentation/DocBook/w1.tmpl > > between

[PATCH] staging: sm750fb: skip unnecessary comparisons

introduced early checks to skip unnecessary comparisons when flags set. Signed-off-by: Lynn Lei --- drivers/staging/sm750fb/sm750.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c index

Re: linux-next: manual merge of the char-misc tree with the jc_docs tree

Hi all, With the merge window opening, just a reminder that this conflict still exists. On Wed, 14 Jun 2017 14:04:16 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the char-misc tree got a conflict in: > > Documentation/DocBook/w1.tmpl > > between commit: > > b4c1064a76e7

Re: [PATCH v8 05/10] mm: thp: enable thp migration in generic path

On 2 Jul 2017, at 13:57, Kirill A. Shutemov wrote: > On Sat, Jul 01, 2017 at 09:40:03AM -0400, Zi Yan wrote: >> --- a/mm/rmap.c >> +++ b/mm/rmap.c >> @@ -1302,6 +1302,7 @@ static bool try_to_unmap_one(struct page *page, struct >> vm_area_struct *vma, >> bool ret = true; >> enum

Re: [PATCH v8 05/10] mm: thp: enable thp migration in generic path

On 2 Jul 2017, at 13:57, Kirill A. Shutemov wrote: > On Sat, Jul 01, 2017 at 09:40:03AM -0400, Zi Yan wrote: >> --- a/mm/rmap.c >> +++ b/mm/rmap.c >> @@ -1302,6 +1302,7 @@ static bool try_to_unmap_one(struct page *page, struct >> vm_area_struct *vma, >> bool ret = true; >> enum

答复: [PATCH v4] mmc: dw_mmc-k3: add sd support for hi3660

Hi,all Sorry to bother you, but could you spare some time to help review patch v5 that I will send later. In this patch，the coding style is further improved and solve guodong's review. Thank you very much. -邮件原件- 发件人: Guodong Xu [mailto:guodong...@linaro.org] 发送时间: 2017年6月30日 21:28

答复: [PATCH v4] mmc: dw_mmc-k3: add sd support for hi3660

Hi,all Sorry to bother you, but could you spare some time to help review patch v5 that I will send later. In this patch，the coding style is further improved and solve guodong's review. Thank you very much. -邮件原件- 发件人: Guodong Xu [mailto:guodong...@linaro.org] 发送时间: 2017年6月30日 21:28

Re: linux-next: manual merge of the tip tree with the kbuild tree

Hi Al, Since part of the tip tree has been merged into the vfs tree, this conflict also applies to the vfs tree, now. On Fri, 23 Jun 2017 13:50:17 +1000 Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > >

Re: linux-next: manual merge of the tip tree with the kbuild tree

Hi Al, Since part of the tip tree has been merged into the vfs tree, this conflict also applies to the vfs tree, now. On Fri, 23 Jun 2017 13:50:17 +1000 Stephen Rothwell wrote: > > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/arm/include/uapi/asm/Kbuild

[PATCH v5] mmc: dw_mmc-k3: add sd support for hi3660

From: Li Wei Add sd card support for hi3660 soc Signed-off-by: Li Wei Signed-off-by: Chen Jun Major changes in v3: - solve review comments from Heiner Kallweit. *use the GENMASK and FIELD_PREP macros replace the bit shift

[PATCH v5] mmc: dw_mmc-k3: add sd support for hi3660

From: Li Wei Add sd card support for hi3660 soc Signed-off-by: Li Wei Signed-off-by: Chen Jun Major changes in v3: - solve review comments from Heiner Kallweit. *use the GENMASK and FIELD_PREP macros replace the bit shift operation. *use usleep_range() replace udelay() and mdelay().

Re: [PATCH v2 8/8] iio: counter: Add support for STM32 LPTimer

On Sat, Jul 01, 2017 at 07:09:17PM +0100, Jonathan Cameron wrote: >On Sat, 1 Jul 2017 09:40:35 -0400 >William Breathitt Gray wrote: > >> On Sat, Jul 01, 2017 at 01:25:18PM +0100, Jonathan Cameron wrote: >> >On Fri, 30 Jun 2017 22:36:48 +0200 >> >Benjamin Gaignard

Re: [PATCH v2 8/8] iio: counter: Add support for STM32 LPTimer

On Sat, Jul 01, 2017 at 07:09:17PM +0100, Jonathan Cameron wrote: >On Sat, 1 Jul 2017 09:40:35 -0400 >William Breathitt Gray wrote: > >> On Sat, Jul 01, 2017 at 01:25:18PM +0100, Jonathan Cameron wrote: >> >On Fri, 30 Jun 2017 22:36:48 +0200 >> >Benjamin Gaignard wrote: >> > >> >> 2017-06-30

linux-next: build warning after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c: In function 'kiblnd_send': drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c:1643:2: warning: ignoring return value of

linux-next: build warning after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c: In function 'kiblnd_send': drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c:1643:2: warning: ignoring return value of

Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe

[+cc Catalin, Will, linux-arm-kernel] Applied patches 2 & 3 to pci/host-kirin for v4.13. I would like a MAINTAINERS update, too. If you send me that, I'll squash it into the driver patch. Catalin, Will, how do you want to handle the arch/arm64/configs/defconfig change (patch 3)? It's

Re: [PATCH v11 0/3]add PCIe driver for Kirin PCIe

[+cc Catalin, Will, linux-arm-kernel] Applied patches 2 & 3 to pci/host-kirin for v4.13. I would like a MAINTAINERS update, too. If you send me that, I'll squash it into the driver patch. Catalin, Will, how do you want to handle the arch/arm64/configs/defconfig change (patch 3)? It's

Linux 4.12

Things were quite calm this week, so I really didn't have any real reason to delay the 4.12 release. As mentioned over the various rc announcements, 4.12 is one of the bigger releases historically, and I think only 4.9 ends up having had more commits. And 4.9 was big at least partly because Greg

Linux 4.12

Things were quite calm this week, so I really didn't have any real reason to delay the 4.12 release. As mentioned over the various rc announcements, 4.12 is one of the bigger releases historically, and I think only 4.9 ends up having had more commits. And 4.9 was big at least partly because Greg

[GIT PULL] uuid updates for 4.13-rc1

Hi Linus, this is a pull request for the new uuid subsystem, in which Amir, Andy and I have started consolidating our uuid/guid helpers and improving the types used for them. Note that various other subsystems have pulled in this tree, so I'd like it to go in early. The following changes since

[GIT PULL] uuid updates for 4.13-rc1

Hi Linus, this is a pull request for the new uuid subsystem, in which Amir, Andy and I have started consolidating our uuid/guid helpers and improving the types used for them. Note that various other subsystems have pulled in this tree, so I'd like it to go in early. The following changes since

Re: [PATCH v9 2/3] PCI: Add tango PCIe host bridge support

On Tue, Jun 20, 2017 at 10:17:40AM +0200, Marc Gonzalez wrote: > This driver is required to work around several hardware bugs > in the PCIe controller. > > NB: Revision 1 does not support legacy interrupts, or IO space. I had to apply these manually because of conflicts in Kconfig and Makefile.

Re: [PATCH v9 2/3] PCI: Add tango PCIe host bridge support

On Tue, Jun 20, 2017 at 10:17:40AM +0200, Marc Gonzalez wrote: > This driver is required to work around several hardware bugs > in the PCIe controller. > > NB: Revision 1 does not support legacy interrupts, or IO space. I had to apply these manually because of conflicts in Kconfig and Makefile.

[PATCH] staging: sm750fb: coordinate conditional compilation

coordinate conditional compilation with g_dcftSupportedDviController[] fix exceed-80-characters issue Signed-off-by: Lynn Lei --- drivers/staging/sm750fb/ddk750_dvi.c | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git

[PATCH] staging: sm750fb: coordinate conditional compilation

coordinate conditional compilation with g_dcftSupportedDviController[] fix exceed-80-characters issue Signed-off-by: Lynn Lei --- drivers/staging/sm750fb/ddk750_dvi.c | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/drivers/staging/sm750fb/ddk750_dvi.c

Re: serial: imx: disable DMA for RS-485 on i.MX6 SMP

Hi Clemens, On Sun, Jul 2, 2017 at 5:47 PM, Clemens Gruber wrote: > The two patches work for me! > > You can add my Tested-by tag if/when you submit them. > > Tested-by: Clemens Gruber Thanks for testing. I will wait a bit longer to

Re: serial: imx: disable DMA for RS-485 on i.MX6 SMP

Hi Clemens, On Sun, Jul 2, 2017 at 5:47 PM, Clemens Gruber wrote: > The two patches work for me! > > You can add my Tested-by tag if/when you submit them. > > Tested-by: Clemens Gruber Thanks for testing. I will wait a bit longer to see if we can fix DMA usage with RS485. Regards, Fabio

Re: [PATCH v2] kbuild: improve comments on KBUILD_SRC

2017-06-30 11:45 GMT+09:00 Cao jin : > Original comments is confusing on "OBJ directory", make it clear. > Bonus: move comments close to what it wants to comment. > > Signed-off-by: Cao jin Applied to linux-kbuild/kbuild. Thanks! -- Best

Re: [PATCH v2] kbuild: improve comments on KBUILD_SRC

2017-06-30 11:45 GMT+09:00 Cao jin : > Original comments is confusing on "OBJ directory", make it clear. > Bonus: move comments close to what it wants to comment. > > Signed-off-by: Cao jin Applied to linux-kbuild/kbuild. Thanks! -- Best Regards Masahiro Yamada

[PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

Variable mode in method wacom_show_remote_mode() is defined as u8, thus statement (mode >= 0) is always true and should be removed, simplifying the logic. Signed-off-by: Christos Gkekas --- drivers/hid/wacom_sys.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-)

[PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

Variable mode in method wacom_show_remote_mode() is defined as u8, thus statement (mode >= 0) is always true and should be removed, simplifying the logic. Signed-off-by: Christos Gkekas --- drivers/hid/wacom_sys.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

Re: [PATCH v4 16/28] tty: serial: owl: Implement console driver

Am 07.06.2017 um 16:37 schrieb Andy Shevchenko: > On Tue, Jun 6, 2017 at 3:54 AM, Andreas Färber wrote: >> Implement serial console driver to complement earlycon. >> >> Based on LeMaker linux-actions tree. > >> +#define OWL_UART_CTL_DWLS_MASK (0x3 << 0) > > GENMASK() ?

Re: [PATCH v4 16/28] tty: serial: owl: Implement console driver

Am 07.06.2017 um 16:37 schrieb Andy Shevchenko: > On Tue, Jun 6, 2017 at 3:54 AM, Andreas Färber wrote: >> Implement serial console driver to complement earlycon. >> >> Based on LeMaker linux-actions tree. > >> +#define OWL_UART_CTL_DWLS_MASK (0x3 << 0) > > GENMASK() ? > >> +#define

Re: [PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

On 02/07/17 15:04:28 -0700, Joe Perches wrote: > On Sun, 2017-07-02 at 22:54 +0100, Christos Gkekas wrote: > > Variable mode in method wacom_show_remote_mode() is defined as u8, thus > > statement (mode >= 0) is always true and should be removed, simplifying > > the logic. > [] > > diff --git

Re: [PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

On 02/07/17 15:04:28 -0700, Joe Perches wrote: > On Sun, 2017-07-02 at 22:54 +0100, Christos Gkekas wrote: > > Variable mode in method wacom_show_remote_mode() is defined as u8, thus > > statement (mode >= 0) is always true and should be removed, simplifying > > the logic. > [] > > diff --git

Re: [PATCH] Input: i8042: add a check in i8042_interrupt

Hi, On Sat, Jun 24, 2017 at 09:38:48AM +, chenhong (N) wrote: > Description of problem: > > Encounterd BUG case: > serio: i8042 KBD port at 0x60,0x64 irq 1 > BUG: unable to handle kernel NULL pointer dereference at 0050 > IP: [] _spin_lock_irqsave+0x1f/0x40 > PGD 0 > Oops: 0002

Re: [PATCH] Input: i8042: add a check in i8042_interrupt

Hi, On Sat, Jun 24, 2017 at 09:38:48AM +, chenhong (N) wrote: > Description of problem: > > Encounterd BUG case: > serio: i8042 KBD port at 0x60,0x64 irq 1 > BUG: unable to handle kernel NULL pointer dereference at 0050 > IP: [] _spin_lock_irqsave+0x1f/0x40 > PGD 0 > Oops: 0002

[PATCH] netxen_nic: Remove unused pointer hdr in netxen_setup_minidump()

Pointer hdr in netxen_setup_minidump() is set but never used, thus should be removed. Signed-off-by: Christos Gkekas --- drivers/net/ethernet/qlogic/netxen/netxen_nic_ctx.c | 3 --- 1 file changed, 3 deletions(-) diff --git

[PATCH] netxen_nic: Remove unused pointer hdr in netxen_setup_minidump()

Pointer hdr in netxen_setup_minidump() is set but never used, thus should be removed. Signed-off-by: Christos Gkekas --- drivers/net/ethernet/qlogic/netxen/netxen_nic_ctx.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/net/ethernet/qlogic/netxen/netxen_nic_ctx.c

Re: [PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

On Sun, 2017-07-02 at 22:54 +0100, Christos Gkekas wrote: > Variable mode in method wacom_show_remote_mode() is defined as u8, thus > statement (mode >= 0) is always true and should be removed, simplifying > the logic. [] > diff --git a/drivers/hid/wacom_sys.c b/drivers/hid/wacom_sys.c [] > @@

Re: [PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

On Sun, 2017-07-02 at 22:54 +0100, Christos Gkekas wrote: > Variable mode in method wacom_show_remote_mode() is defined as u8, thus > statement (mode >= 0) is always true and should be removed, simplifying > the logic. [] > diff --git a/drivers/hid/wacom_sys.c b/drivers/hid/wacom_sys.c [] > @@

[PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

Variable mode in method wacom_show_remote_mode() is defined as u8, thus statement (mode >= 0) is always true and should be removed, simplifying the logic. Signed-off-by: Christos Gkekas --- drivers/hid/wacom_sys.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-)

[PATCH] HID: wacom: Remove comparison of u8 mode with zero and simplify.

Variable mode in method wacom_show_remote_mode() is defined as u8, thus statement (mode >= 0) is always true and should be removed, simplifying the logic. Signed-off-by: Christos Gkekas --- drivers/hid/wacom_sys.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH] drm/bochs: switch fb_ops over to use drm_fb_helper_cfb helpers

The current drm_fb_helper_sys helpers referenced in fb_ops assume that the video memory is in system RAM. This is not the case for sparc which uses direct physical memory accesses for IO memory and causes the bochs_drm module to panic immediately upon startup as it tries to initialise the

[PATCH] drm/bochs: switch fb_ops over to use drm_fb_helper_cfb helpers

The current drm_fb_helper_sys helpers referenced in fb_ops assume that the video memory is in system RAM. This is not the case for sparc which uses direct physical memory accesses for IO memory and causes the bochs_drm module to panic immediately upon startup as it tries to initialise the

Re: [PATCH 5/6] i2c: pca-platform: use device_property_read_u32

On 30/06/17 22:56, Andy Shevchenko wrote: > On Fri, Jun 30, 2017 at 12:03 PM, Wolfram Sang wrote: >> - i2c->algo_data.i2c_clock = 59000; + ret = device_property_read_u32(>dev, "clock-frequency", +

Re: [PATCH 5/6] i2c: pca-platform: use device_property_read_u32

On 30/06/17 22:56, Andy Shevchenko wrote: > On Fri, Jun 30, 2017 at 12:03 PM, Wolfram Sang wrote: >> - i2c->algo_data.i2c_clock = 59000; + ret = device_property_read_u32(>dev, "clock-frequency", +

Re: [PATCH] PCI: xilinx: make of_device_ids const.

On Tue, Jun 20, 2017 at 11:17:48AM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH] PCI: xilinx: make of_device_ids const.

On Tue, Jun 20, 2017 at 11:17:48AM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH] PCI: rcar-gen2: make of_device_ids const

On Fri, Jun 23, 2017 at 02:59:52PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [PATCH] PCI: rcar-gen2: make of_device_ids const

On Fri, Jun 23, 2017 at 02:59:52PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav Applied with acks

Re: [PATCH] PCI: dwc: qcom: limit TPL size to 2K to fix hw issue

On Thu, Jun 29, 2017 at 05:34:55PM +0200, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch limits TPL size to 2K from default 4K size as a workaround > for a HW bug in v0 version of pcie IP. When using default TPL size of 4K > the

Re: [PATCH] PCI: dwc: qcom: limit TPL size to 2K to fix hw issue

On Thu, Jun 29, 2017 at 05:34:55PM +0200, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch limits TPL size to 2K from default 4K size as a workaround > for a HW bug in v0 version of pcie IP. When using default TPL size of 4K > the internal buffer gets corrupted

Re: [PATCH 3/6] i2c: pca-platform: propagate error from i2c_pca_add_numbered_bus

On 30/06/17 20:40, Andy Shevchenko wrote: > On Fri, Jun 30, 2017 at 3:54 AM, Chris Packham > wrote: >> Rather than returning -ENODEV if i2c_pca_add_numbered_bus() fails, >> propagate the error to aid debugging. >> > > + Suggested-by ? > > You or Wolfram can

Re: [PATCH 3/6] i2c: pca-platform: propagate error from i2c_pca_add_numbered_bus

On 30/06/17 20:40, Andy Shevchenko wrote: > On Fri, Jun 30, 2017 at 3:54 AM, Chris Packham > wrote: >> Rather than returning -ENODEV if i2c_pca_add_numbered_bus() fails, >> propagate the error to aid debugging. >> > > + Suggested-by ? > > You or Wolfram can use below if you agree on it (I'm

Re: [PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

On Sun, Jul 2, 2017 at 10:49 PM, Janusz Lisiecki wrote: > W dniu 2017-07-02 o 21:38, Luc Van Oostenryck pisze: > >> On Sun, Jul 2, 2017 at 4:27 PM, Janusz Lisiecki >> wrote: >>> >>> This patch fixes the following Sparse warnings in

Re: [PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

On Sun, Jul 2, 2017 at 10:49 PM, Janusz Lisiecki wrote: > W dniu 2017-07-02 o 21:38, Luc Van Oostenryck pisze: > >> On Sun, Jul 2, 2017 at 4:27 PM, Janusz Lisiecki >> wrote: >>> >>> This patch fixes the following Sparse warnings in ks_wlan_net.c: >>> drivers/staging/ks7010/ks_wlan_net.c:1359:24:

Re: [PATCH 2/4] ARM/PCI: mv78xx0: pass pci_ops correctly again

On Sat, Jul 01, 2017 at 02:54:57PM +0100, Lorenzo Pieralisi wrote: > Hi Bjorn, > > On Tue, Jun 27, 2017 at 06:11:43PM -0500, Bjorn Helgaas wrote: > > On Thu, Jun 22, 2017 at 10:38:55AM +0100, Lorenzo Pieralisi wrote: > > > On Wed, Jun 21, 2017 at 11:53:00PM +0200, Arnd Bergmann wrote: > > > > We

Re: [PATCH 2/4] ARM/PCI: mv78xx0: pass pci_ops correctly again

On Sat, Jul 01, 2017 at 02:54:57PM +0100, Lorenzo Pieralisi wrote: > Hi Bjorn, > > On Tue, Jun 27, 2017 at 06:11:43PM -0500, Bjorn Helgaas wrote: > > On Thu, Jun 22, 2017 at 10:38:55AM +0100, Lorenzo Pieralisi wrote: > > > On Wed, Jun 21, 2017 at 11:53:00PM +0200, Arnd Bergmann wrote: > > > > We

[PATCH] PCI: Work around poweroff & suspend-to-RAM issue on Macbook Pro 11

Neither soft poweroff (transition to ACPI power state S5) nor suspend-to-RAM (transition to state S3) works on the Macbook Pro 11,4 and 11,5. The problem is related to the [mem 0x7fa0-0x7fbf] space. When we use that space, e.g., by assigning it to the 00:1c.0 Root Port, the ACPI Power

[PATCH] PCI: Work around poweroff & suspend-to-RAM issue on Macbook Pro 11

Neither soft poweroff (transition to ACPI power state S5) nor suspend-to-RAM (transition to state S3) works on the Macbook Pro 11,4 and 11,5. The problem is related to the [mem 0x7fa0-0x7fbf] space. When we use that space, e.g., by assigning it to the 00:1c.0 Root Port, the ACPI Power

Re: [PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

W dniu 2017-07-02 o 21:38, Luc Van Oostenryck pisze: On Sun, Jul 2, 2017 at 4:27 PM, Janusz Lisiecki wrote: This patch fixes the following Sparse warnings in ks_wlan_net.c: drivers/staging/ks7010/ks_wlan_net.c:1359:24: warning: cast to restricted __le16 Both sides of

Re: [PATCH 1/1] staging: ks7010: Fix cast to restricted __le16 in ks_wlan_net.c

W dniu 2017-07-02 o 21:38, Luc Van Oostenryck pisze: On Sun, Jul 2, 2017 at 4:27 PM, Janusz Lisiecki wrote: This patch fixes the following Sparse warnings in ks_wlan_net.c: drivers/staging/ks7010/ks_wlan_net.c:1359:24: warning: cast to restricted __le16 Both sides of assignment are u16 so (as

Re: serial: imx: disable DMA for RS-485 on i.MX6 SMP

Hi Fabio, On Tue, Jun 20, 2017 at 08:49:28PM -0300, Fabio Estevam wrote: > Hi Clemens, > > On Tue, Jun 20, 2017 at 1:13 PM, Fabio Estevam wrote: > > > The subject gives the impression that the DMA will only be disabled > > for RS485, but the impact of this change is wider.

Re: serial: imx: disable DMA for RS-485 on i.MX6 SMP

Hi Fabio, On Tue, Jun 20, 2017 at 08:49:28PM -0300, Fabio Estevam wrote: > Hi Clemens, > > On Tue, Jun 20, 2017 at 1:13 PM, Fabio Estevam wrote: > > > The subject gives the impression that the DMA will only be disabled > > for RS485, but the impact of this change is wider. > > > > For example:

Re: [PATCH RESEND] input: gpio_keys: handle the missing key press event in resume phase

On Wed, Jun 28, 2017 at 12:29:40PM +0200, Enric Balletbo i Serra wrote: > From: Joseph Lo > > The GPIO key press event might be missed in the resume phase, if the key > had been released before the system had been resumed to the stage that it > could capture the press event.

Re: [PATCH RESEND] input: gpio_keys: handle the missing key press event in resume phase

On Wed, Jun 28, 2017 at 12:29:40PM +0200, Enric Balletbo i Serra wrote: > From: Joseph Lo > > The GPIO key press event might be missed in the resume phase, if the key > had been released before the system had been resumed to the stage that it > could capture the press event. So we simulate the

Re: [PATCH] of_mdio: Fix broken PHY IRQ in case of probe deferral

On Tue, Jun 6, 2017 at 11:43 AM, Geert Uytterhoeven wrote: > On Tue, May 23, 2017 at 11:36 AM, Geert Uytterhoeven > wrote: >> On Fri, May 19, 2017 at 12:21 AM, Florian Fainelli >> wrote: >>> On 05/18/2017 01:36 PM, Geert

Re: [PATCH] of_mdio: Fix broken PHY IRQ in case of probe deferral

On Tue, Jun 6, 2017 at 11:43 AM, Geert Uytterhoeven wrote: > On Tue, May 23, 2017 at 11:36 AM, Geert Uytterhoeven > wrote: >> On Fri, May 19, 2017 at 12:21 AM, Florian Fainelli >> wrote: >>> On 05/18/2017 01:36 PM, Geert Uytterhoeven wrote: On Thu, May 18, 2017 at 9:34 PM, Andrew Lunn

Re: [PATCH v4 16/28] tty: serial: owl: Implement console driver

Am 06.06.2017 um 15:34 schrieb Alan Cox: >> +static void owl_uart_set_termios(struct uart_port *port, >> + struct ktermios *termios, >> + struct ktermios *old) >> +{ >> +struct owl_uart_port *owl_port = to_owl_uart_port(port); >> +

Re: [PATCH v4 16/28] tty: serial: owl: Implement console driver

Am 06.06.2017 um 15:34 schrieb Alan Cox: >> +static void owl_uart_set_termios(struct uart_port *port, >> + struct ktermios *termios, >> + struct ktermios *old) >> +{ >> +struct owl_uart_port *owl_port = to_owl_uart_port(port); >> +

<    1   2   3   4   5   >