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

On Fri, Apr 21, 2017 at 2:54 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the pm tree got a conflict in: > > include/dt-bindings/genpd/k2g.h > > between commit: > > 7cc119f29b19 ("dt-bindings: Add TI SCI PM Domains") > > from the arm-soc tree

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

On Fri, Apr 21, 2017 at 2:54 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the pm tree got a conflict in: > > include/dt-bindings/genpd/k2g.h > > between commit: > > 7cc119f29b19 ("dt-bindings: Add TI SCI PM Domains") > > from the arm-soc tree and commit: > >

Re: [PATCH 05/28] drm/bridge: fix include notation and remove -Iinclude/drm flag

Hi Masahiro, On 20.04.2017 11:56, Masahiro Yamada wrote: > Include instead of relative path from include/drm, then > remove the -Iinclude/drm compiler flag. > > Signed-off-by: Masahiro Yamada > --- > > drivers/gpu/drm/bridge/Makefile| 2 -- >

Re: [PATCH 05/28] drm/bridge: fix include notation and remove -Iinclude/drm flag

Hi Masahiro, On 20.04.2017 11:56, Masahiro Yamada wrote: > Include instead of relative path from include/drm, then > remove the -Iinclude/drm compiler flag. > > Signed-off-by: Masahiro Yamada > --- > > drivers/gpu/drm/bridge/Makefile| 2 -- > drivers/gpu/drm/bridge/nxp-ptn3460.c |

[PATCH 2/3] crypto: cavium: Remove the individual encrypt/decrypt function for each algorithm

Remove the individual encrypt/decrypt function for easch algorithm. This is in prepration of adding more crypto algorithms supported by hardware. While at that simplify create_ctx_hdr/create_input_list function interfaces. Signed-off-by: George Cherian ---

[PATCH 2/3] crypto: cavium: Remove the individual encrypt/decrypt function for each algorithm

Remove the individual encrypt/decrypt function for easch algorithm. This is in prepration of adding more crypto algorithms supported by hardware. While at that simplify create_ctx_hdr/create_input_list function interfaces. Signed-off-by: George Cherian --- drivers/crypto/cavium/cpt/cptvf_algs.c

[PATCH 1/3] crypto: cavium: Downgrade the annoying misc interrupt print from dev_err to dev_dbg

Mailbox interrupt is common and it is not an error interrupt. So downgrade the print from dev_err to dev_dbg. Signed-off-by: George Cherian --- drivers/crypto/cavium/cpt/cptvf_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/3] crypto: cavium: Downgrade the annoying misc interrupt print from dev_err to dev_dbg

Mailbox interrupt is common and it is not an error interrupt. So downgrade the print from dev_err to dev_dbg. Signed-off-by: George Cherian --- drivers/crypto/cavium/cpt/cptvf_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/cavium/cpt/cptvf_main.c

[PATCH 0/3] Add more algorithms and some misc cleanups

This series adds more algorithem support for CPT. Add support for -ecb(aes) -cfb(aes) -ecb(des3_ede) Some cleanups too. George Cherian (3): crypto: cavium: Downgrade the annoying misc interrupt print from dev_err to dev_dbg crypto: cavium: Remove the individual

[PATCH 0/3] Add more algorithms and some misc cleanups

This series adds more algorithem support for CPT. Add support for -ecb(aes) -cfb(aes) -ecb(des3_ede) Some cleanups too. George Cherian (3): crypto: cavium: Downgrade the annoying misc interrupt print from dev_err to dev_dbg crypto: cavium: Remove the individual

[PATCH 3/3] crypto: cavium: Add more algorithms

Add more algorithm support for the driver. Add support for ecb(aes), cfb(aes) and ecb(des3_ede). Signed-off-by: George Cherian --- drivers/crypto/cavium/cpt/cptvf_algs.c | 63 ++ 1 file changed, 63 insertions(+) diff --git

[PATCH 3/3] crypto: cavium: Add more algorithms

Add more algorithm support for the driver. Add support for ecb(aes), cfb(aes) and ecb(des3_ede). Signed-off-by: George Cherian --- drivers/crypto/cavium/cpt/cptvf_algs.c | 63 ++ 1 file changed, 63 insertions(+) diff --git

Re: [PATCH v3] scsi/bfa: use designated initializers

Looks good, Reviewed-by: Christoph Hellwig

Re: [PATCH v3] scsi/bfa: use designated initializers

Looks good, Reviewed-by: Christoph Hellwig

Re: [PATCH V5 4/7] ARM: pxa: Use - instead of @ for DT OPP entries

On 20-04-17, 22:14, Robert Jarzmik wrote: > Viresh Kumar writes: > > > Compiling the DT file with W=1, DTC warns like follows: > > > > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a > > unit name, but no reg property > > > > Fix this by replacing

Re: [PATCH V5 4/7] ARM: pxa: Use - instead of @ for DT OPP entries

On 20-04-17, 22:14, Robert Jarzmik wrote: > Viresh Kumar writes: > > > Compiling the DT file with W=1, DTC warns like follows: > > > > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a > > unit name, but no reg property > > > > Fix this by replacing '@' with '-' as the OPP

Re: [PATCH V5 3/7] ARM: exynos: Use - instead of @ for DT OPP entries

On 20-04-17, 18:09, Krzysztof Kozlowski wrote: > On Thu, Apr 20, 2017 at 04:25:07PM +0530, Viresh Kumar wrote: > > Compiling the DT file with W=1, DTC warns like follows: > > > > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a > > unit name, but no reg property > > > > Fix

Re: [PATCH V5 3/7] ARM: exynos: Use - instead of @ for DT OPP entries

On 20-04-17, 18:09, Krzysztof Kozlowski wrote: > On Thu, Apr 20, 2017 at 04:25:07PM +0530, Viresh Kumar wrote: > > Compiling the DT file with W=1, DTC warns like follows: > > > > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a > > unit name, but no reg property > > > > Fix

Re: [PATCH net-next v3] bindings: net: stmmac: add missing note about LPI interrupt

On 4/18/2017 2:39 PM, Niklas Cassel wrote: From: Niklas Cassel The hardware has a LPI interrupt. There is already code in the stmmac driver to parse and handle the interrupt. However, this information was missing from the DT binding. At the same time, improve the

Re: [PATCH net-next v3] bindings: net: stmmac: add missing note about LPI interrupt

On 4/18/2017 2:39 PM, Niklas Cassel wrote: From: Niklas Cassel The hardware has a LPI interrupt. There is already code in the stmmac driver to parse and handle the interrupt. However, this information was missing from the DT binding. At the same time, improve the description of the existing

Re: [PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

On Fri, Apr 21, 2017 at 01:09:59AM -0400, Matt Brown wrote: > On 04/20/2017 01:41 PM, Serge E. Hallyn wrote: > >Quoting m...@nmatt.com (m...@nmatt.com): > >>On 2017-04-20 11:19, Serge E. Hallyn wrote: > >>>Quoting Matt Brown (m...@nmatt.com): > On 04/19/2017 07:53 PM, Serge E. Hallyn wrote: >

Re: [PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

On Fri, Apr 21, 2017 at 01:09:59AM -0400, Matt Brown wrote: > On 04/20/2017 01:41 PM, Serge E. Hallyn wrote: > >Quoting m...@nmatt.com (m...@nmatt.com): > >>On 2017-04-20 11:19, Serge E. Hallyn wrote: > >>>Quoting Matt Brown (m...@nmatt.com): > On 04/19/2017 07:53 PM, Serge E. Hallyn wrote: >

Re: [PATCH] Added paranthesis around complex define statements

On Fri, Apr 21, 2017 at 05:15:46AM +, Andriy Gelman wrote: > This is a patch to the ks_wlan_ioctl.h file that fixes paranthesis error > found by the checkpatch.pl tool No, it also does other things :( Also, please fix up the subject to look like other patches done for this file/driver. And

Re: [PATCH] Added paranthesis around complex define statements

On Fri, Apr 21, 2017 at 05:15:46AM +, Andriy Gelman wrote: > This is a patch to the ks_wlan_ioctl.h file that fixes paranthesis error > found by the checkpatch.pl tool No, it also does other things :( Also, please fix up the subject to look like other patches done for this file/driver. And

[PATCH] Added paranthesis around complex define statements

This is a patch to the ks_wlan_ioctl.h file that fixes paranthesis error found by the checkpatch.pl tool Signed-off-by: Andriy Gelman --- drivers/staging/ks7010/ks_wlan_ioctl.h | 53 +- 1 file changed, 26 insertions(+), 27 deletions(-)

[PATCH] Added paranthesis around complex define statements

This is a patch to the ks_wlan_ioctl.h file that fixes paranthesis error found by the checkpatch.pl tool Signed-off-by: Andriy Gelman --- drivers/staging/ks7010/ks_wlan_ioctl.h | 53 +- 1 file changed, 26 insertions(+), 27 deletions(-) diff --git

Re: [PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

On 04/20/2017 01:41 PM, Serge E. Hallyn wrote: Quoting m...@nmatt.com (m...@nmatt.com): On 2017-04-20 11:19, Serge E. Hallyn wrote: Quoting Matt Brown (m...@nmatt.com): On 04/19/2017 07:53 PM, Serge E. Hallyn wrote: Quoting Matt Brown (m...@nmatt.com): On 04/19/2017 12:58 AM, Serge E.

Re: [PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

On 04/20/2017 01:41 PM, Serge E. Hallyn wrote: Quoting m...@nmatt.com (m...@nmatt.com): On 2017-04-20 11:19, Serge E. Hallyn wrote: Quoting Matt Brown (m...@nmatt.com): On 04/19/2017 07:53 PM, Serge E. Hallyn wrote: Quoting Matt Brown (m...@nmatt.com): On 04/19/2017 12:58 AM, Serge E.

[PATCH 05/13] sparc/PCI: Keep resource idx order with bridge register number

On one system found strange "no compatible bridge window" warning even we already had pref_compat support that add extra pref bit for device resource. PCI: Claiming :00:01.0: Resource 14: 00020001..000200010fff [10220c] PCI: Claiming :01:00.0: Resource 1:

[PATCH 05/13] sparc/PCI: Keep resource idx order with bridge register number

On one system found strange "no compatible bridge window" warning even we already had pref_compat support that add extra pref bit for device resource. PCI: Claiming :00:01.0: Resource 14: 00020001..000200010fff [10220c] PCI: Claiming :01:00.0: Resource 1:

[PATCH 00/13] PCI: sparc related 64bit resource fixup

Hi Bjorn, Please check sparc related 64bit resource handling patches. patch 1-8: parse MEM64 for sparc and other system with OF. So device 64bit resource could find their parent resource. patch 9-12: MMIO64 handling enhancement treat non-pref mmio64 as pref mmio64 if all bridges

[PATCH 00/13] PCI: sparc related 64bit resource fixup

Hi Bjorn, Please check sparc related 64bit resource handling patches. patch 1-8: parse MEM64 for sparc and other system with OF. So device 64bit resource could find their parent resource. patch 9-12: MMIO64 handling enhancement treat non-pref mmio64 as pref mmio64 if all bridges

[PATCH 07/13] powerpc/PCI: Add IORESOURCE_MEM_64 for 64-bit resource in OF parsing

For device resource PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource. This patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

[PATCH 07/13] powerpc/PCI: Add IORESOURCE_MEM_64 for 64-bit resource in OF parsing

For device resource PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource. This patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

[PATCH 01/13] sparc/PCI: Use correct offset for bus address to resource

After we added 64bit mmio parsing, we got some "no compatible bridge window" warning on anther new model that support 64bit resource. It turns out that we can not use mem_space.start as 64bit mem space offset, aka there is mem_space.start != offset. Use child_phys_addr to calculate exact offset

[PATCH 01/13] sparc/PCI: Use correct offset for bus address to resource

After we added 64bit mmio parsing, we got some "no compatible bridge window" warning on anther new model that support 64bit resource. It turns out that we can not use mem_space.start as 64bit mem space offset, aka there is mem_space.start != offset. Use child_phys_addr to calculate exact offset

[PATCH 12/13] PCI: Only treat non-pref mmio64 as pref if host bridge has mmio64

If host bridge does not have mmio64 above 4G, We don't need to treat device non-pref mmio64 as as pref mmio64. Signed-off-by: Yinghai Lu Tested-by: Khalid Aziz --- drivers/pci/setup-bus.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 02/13] PCI: Add pci_find_bus_resource()

Add pci_find_bus_resource() to return bus resource for input resource. In some case, we may only have bus instead of dev. It is same as pci_find_parent_resource, but take bus as input. Signed-off-by: Yinghai Lu --- drivers/pci/pci.c | 27 ---

[PATCH 12/13] PCI: Only treat non-pref mmio64 as pref if host bridge has mmio64

If host bridge does not have mmio64 above 4G, We don't need to treat device non-pref mmio64 as as pref mmio64. Signed-off-by: Yinghai Lu Tested-by: Khalid Aziz --- drivers/pci/setup-bus.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/setup-bus.c

[PATCH 02/13] PCI: Add pci_find_bus_resource()

Add pci_find_bus_resource() to return bus resource for input resource. In some case, we may only have bus instead of dev. It is same as pci_find_parent_resource, but take bus as input. Signed-off-by: Yinghai Lu --- drivers/pci/pci.c | 27 --- include/linux/pci.h | 2

[PATCH 09/13] PCI: Check pref compatible bit for mem64 resource of PCIe device

We still get "no compatible bridge window" warning on sparc T5-8 after we add support for 64bit resource parsing for root bus. PCI: scan_bus[/pci@300/pci@1/pci@0/pci@6] bus no 8 PCI: Claiming :00:01.0: Resource 15: 8001..8004afff [220c] PCI: Claiming :01:00.0:

[PATCH 09/13] PCI: Check pref compatible bit for mem64 resource of PCIe device

We still get "no compatible bridge window" warning on sparc T5-8 after we add support for 64bit resource parsing for root bus. PCI: scan_bus[/pci@300/pci@1/pci@0/pci@6] bus no 8 PCI: Claiming :00:01.0: Resource 15: 8001..8004afff [220c] PCI: Claiming :01:00.0:

[PATCH 10/13] PCI: Only treat non-pref mmio64 as pref if all bridges have MEM_64

If any bridge up to root only have 32bit pref mmio, We don't need to treat device non-pref mmio64 as as pref mmio64. We need to move pci_bridge_check_ranges calling early. For parent bridges pref mmio BAR may not allocated by BIOS, res flags is still 0, we need to have it correct set before we

[PATCH 10/13] PCI: Only treat non-pref mmio64 as pref if all bridges have MEM_64

If any bridge up to root only have 32bit pref mmio, We don't need to treat device non-pref mmio64 as as pref mmio64. We need to move pci_bridge_check_ranges calling early. For parent bridges pref mmio BAR may not allocated by BIOS, res flags is still 0, we need to have it correct set before we

Re: [PATCH] ASoC: rsnd: fix semicolon.cocci warnings

Hi > sound/soc/sh/rcar/adg.c:462:54-55: Unneeded semicolon > > > Remove unneeded semicolon. > > Generated by: scripts/coccinelle/misc/semicolon.cocci > > CC: Kuninori Morimoto > Signed-off-by: Fengguang Wu Where is my brown paper

[PATCH 06/13] powerpc/PCI: Keep resource idx order with bridge register number

Same as sparc version. Make resource with consistent sequence like other arch or directly from pci_read_bridge_bases(), even when non-pref mmio is missing, or out of ordering in firmware reporting. Just hold i = 1 for non pref mmio, and i = 2 for pref mmio. Signed-off-by: Yinghai Lu

[PATCH 04/13] sparc/PCI: Add IORESOURCE_MEM_64 for 64-bit resource in OF parsing

For device resource with PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource. so this patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

[PATCH 08/13] OF/PCI: Add IORESOURCE_MEM_64 for 64-bit resource

For device resource PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource. This patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

Re: [PATCH] ASoC: rsnd: fix semicolon.cocci warnings

Hi > sound/soc/sh/rcar/adg.c:462:54-55: Unneeded semicolon > > > Remove unneeded semicolon. > > Generated by: scripts/coccinelle/misc/semicolon.cocci > > CC: Kuninori Morimoto > Signed-off-by: Fengguang Wu Where is my brown paper bag ? Acked-by: Kuninori Morimoto > --- > > adg.c |

[PATCH 06/13] powerpc/PCI: Keep resource idx order with bridge register number

Same as sparc version. Make resource with consistent sequence like other arch or directly from pci_read_bridge_bases(), even when non-pref mmio is missing, or out of ordering in firmware reporting. Just hold i = 1 for non pref mmio, and i = 2 for pref mmio. Signed-off-by: Yinghai Lu Cc:

[PATCH 04/13] sparc/PCI: Add IORESOURCE_MEM_64 for 64-bit resource in OF parsing

For device resource with PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource. so this patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

[PATCH 08/13] OF/PCI: Add IORESOURCE_MEM_64 for 64-bit resource

For device resource PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource. This patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

[PATCH 13/13] PCI: Restore pref MMIO allocation logic for host bridge without mmio64

>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources), we change the logic for pref mmio allocation: When bridge pref support mmio64, we will only put children pref that support mmio64 into it, and will put children pref mmio32 into bridge's non-pref mmio32. That

[PATCH 13/13] PCI: Restore pref MMIO allocation logic for host bridge without mmio64

>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources), we change the logic for pref mmio allocation: When bridge pref support mmio64, we will only put children pref that support mmio64 into it, and will put children pref mmio32 into bridge's non-pref mmio32. That

[PATCH 11/13] PCI: Add has_mem64 for struct host_bridge

Add has_mem64 for struct host_bridge, on root bus that does not support mmio64 above 4g, will not set that. We will use that info next two following patches: 1. Don't treat non-pref mmio64 as pref mmio, so will not put it under bridge's pref range when rescan the devices 2. will keep pref

[PATCH 11/13] PCI: Add has_mem64 for struct host_bridge

Add has_mem64 for struct host_bridge, on root bus that does not support mmio64 above 4g, will not set that. We will use that info next two following patches: 1. Don't treat non-pref mmio64 as pref mmio, so will not put it under bridge's pref range when rescan the devices 2. will keep pref

[PATCH 03/13] sparc/PCI: Reserve legacy mmio after PCI mmio

On one system found bunch of claim resource fail from pci device. pci_sun4v f02b894c: PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus address [0x-0xfff]) pci_bus :00: root bus resource [mem 0x2-0x27eff]

[PATCH 03/13] sparc/PCI: Reserve legacy mmio after PCI mmio

On one system found bunch of claim resource fail from pci device. pci_sun4v f02b894c: PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus address [0x-0xfff]) pci_bus :00: root bus resource [mem 0x2-0x27eff]

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

Thanks Stephen. Looks good to me. Logan On 20/04/17 08:10 PM, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in > initializer

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

Thanks Stephen. Looks good to me. Logan On 20/04/17 08:10 PM, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/tee/tee_shm.c:87:2: error: unknown field 'kmap_atomic' specified in > initializer

[PATCH] ASoC: rsnd: fix semicolon.cocci warnings

sound/soc/sh/rcar/adg.c:462:54-55: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Kuninori Morimoto Signed-off-by: Fengguang Wu --- adg.c |2 +- 1 file changed, 1

[PATCH] ASoC: rsnd: fix semicolon.cocci warnings

sound/soc/sh/rcar/adg.c:462:54-55: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Kuninori Morimoto Signed-off-by: Fengguang Wu --- adg.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/sound/soc/sh/rcar/adg.c +++

Re: [PATCH v3] kbuild: Add support to generate LLVM bitcode files

Hi Matthias, 2017-04-05 2:27 GMT+09:00 Matthias Kaehlcke : > From: Vinícius Tinti > > Add rules to kbuild in order to generate LLVM bitcode files with the .ll > extension when using clang. First, I'd like to be sure about the terminology "LLVM

Re: [PATCH v3] kbuild: Add support to generate LLVM bitcode files

Hi Matthias, 2017-04-05 2:27 GMT+09:00 Matthias Kaehlcke : > From: Vinícius Tinti > > Add rules to kbuild in order to generate LLVM bitcode files with the .ll > extension when using clang. First, I'd like to be sure about the terminology "LLVM bitcode" because "bitcode" sounds like

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

On Thu, Apr 20, 2017 at 4:07 PM, Stephen Bates wrote: >>> Yes, this makes sense I think we really just want to distinguish host >>> memory or not in terms of the dev_pagemap type. >> >>> I would like to see mutually exclusive flags for host memory (or not) and >>>

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

On Thu, Apr 20, 2017 at 4:07 PM, Stephen Bates wrote: >>> Yes, this makes sense I think we really just want to distinguish host >>> memory or not in terms of the dev_pagemap type. >> >>> I would like to see mutually exclusive flags for host memory (or not) and >>> persistence (or not). >>> >>

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

On Fri, Apr 21, 2017 at 02:45:40PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in: > > drivers/misc/Makefile > > between commit: > > 58c89c8aa0e8 ("misc: Add host side PCI driver for PCI test function device") > > from the pci

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

On Fri, Apr 21, 2017 at 02:45:40PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in: > > drivers/misc/Makefile > > between commit: > > 58c89c8aa0e8 ("misc: Add host side PCI driver for PCI test function device") > > from the pci

[GIT PULL] Please pull powerpc/linux.git powerpc-4.11-8 tag

Hi Linus, Please pull two final powerpc fixes for 4.11: The following changes since commit 4749228f022893faf54a3dbc70796f78b7d4f342: powerpc/crypto/crc32c-vpmsum: Fix missing preempt_disable() (2017-04-07 21:12:58 +1000) are available in the git repository at:

[GIT PULL] Please pull powerpc/linux.git powerpc-4.11-8 tag

Hi Linus, Please pull two final powerpc fixes for 4.11: The following changes since commit 4749228f022893faf54a3dbc70796f78b7d4f342: powerpc/crypto/crc32c-vpmsum: Fix missing preempt_disable() (2017-04-07 21:12:58 +1000) are available in the git repository at:

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

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/misc/Makefile between commit: 58c89c8aa0e8 ("misc: Add host side PCI driver for PCI test function device") from the pci tree and commits: 6c4e97678501 ("drivers/misc: Add Aspeed LPC control driver")

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

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/misc/Makefile between commit: 58c89c8aa0e8 ("misc: Add host side PCI driver for PCI test function device") from the pci tree and commits: 6c4e97678501 ("drivers/misc: Add Aspeed LPC control driver")

Re: [LTP] [lkp-robot] [KEYS] bdf7c0f8bf: ltp.add_key02.fail

Hi Cyril, On Thu, Apr 20, 2017 at 02:57:50PM +0200, Cyril Hrubis wrote: > > > > In my opinion this is a valid behavior, and the test is just weird; it's > > passing > > in *both* an unaddressable payload and an invalid description, so it's not > > clear > > which case it's meant to be testing.

Re: [LTP] [lkp-robot] [KEYS] bdf7c0f8bf: ltp.add_key02.fail

Hi Cyril, On Thu, Apr 20, 2017 at 02:57:50PM +0200, Cyril Hrubis wrote: > > > > In my opinion this is a valid behavior, and the test is just weird; it's > > passing > > in *both* an unaddressable payload and an invalid description, so it's not > > clear > > which case it's meant to be testing.

Re: your mail

On Thu, Apr 20, 2017 at 09:28:20AM +0200, Michal Hocko wrote: > On Thu 20-04-17 10:27:55, Joonsoo Kim wrote: > > On Mon, Apr 17, 2017 at 10:15:15AM +0200, Michal Hocko wrote: > [...] > > > Which pfn walkers you have in mind? > > > > For example, kpagecount_read() in fs/proc/page.c. I searched it

Re: your mail

On Thu, Apr 20, 2017 at 09:28:20AM +0200, Michal Hocko wrote: > On Thu 20-04-17 10:27:55, Joonsoo Kim wrote: > > On Mon, Apr 17, 2017 at 10:15:15AM +0200, Michal Hocko wrote: > [...] > > > Which pfn walkers you have in mind? > > > > For example, kpagecount_read() in fs/proc/page.c. I searched it

Re: [PATCH v5 04/11] mm: thp: introduce CONFIG_ARCH_ENABLE_THP_MIGRATION

On 04/21/2017 02:17 AM, Zi Yan wrote: > From: Naoya Horiguchi > > Introduces CONFIG_ARCH_ENABLE_THP_MIGRATION to limit thp migration > functionality to x86_64, which should be safer at the first step. > > Signed-off-by: Naoya Horiguchi

Re: [PATCH v5 04/11] mm: thp: introduce CONFIG_ARCH_ENABLE_THP_MIGRATION

On 04/21/2017 02:17 AM, Zi Yan wrote: > From: Naoya Horiguchi > > Introduces CONFIG_ARCH_ENABLE_THP_MIGRATION to limit thp migration > functionality to x86_64, which should be safer at the first step. > > Signed-off-by: Naoya Horiguchi Aneesh's latest HugeTLB migration enablement on powerpc

Re: [PATCH 3.18 000/124] 3.18.50-stable review

On Thu, Apr 20, 2017 at 08:38:16PM -0700, Guenter Roeck wrote: > On 04/20/2017 12:53 PM, Greg Kroah-Hartman wrote: > > On Thu, Apr 20, 2017 at 04:28:03PM +0200, Greg Kroah-Hartman wrote: > > > On Thu, Apr 20, 2017 at 06:46:11AM -0700, Guenter Roeck wrote: > > > > On 04/19/2017 11:34 PM, Greg

Re: [PATCH 3.18 000/124] 3.18.50-stable review

On Thu, Apr 20, 2017 at 08:38:16PM -0700, Guenter Roeck wrote: > On 04/20/2017 12:53 PM, Greg Kroah-Hartman wrote: > > On Thu, Apr 20, 2017 at 04:28:03PM +0200, Greg Kroah-Hartman wrote: > > > On Thu, Apr 20, 2017 at 06:46:11AM -0700, Guenter Roeck wrote: > > > > On 04/19/2017 11:34 PM, Greg

[PATCH] hwmon: (ibmpowernv) Add min/max attributes and current sensors

Add support for adding min/max values for the inband sensors copied by OCC to main memory. And also add current(mA) sensors to the list. Signed-off-by: Shilpasri G Bhat --- drivers/hwmon/ibmpowernv.c | 55 -- 1 file

[PATCH] hwmon: (ibmpowernv) Add min/max attributes and current sensors

Add support for adding min/max values for the inband sensors copied by OCC to main memory. And also add current(mA) sensors to the list. Signed-off-by: Shilpasri G Bhat --- drivers/hwmon/ibmpowernv.c | 55 -- 1 file changed, 53 insertions(+), 2

Re: [PATCH v5 03/11] mm: thp: introduce separate TTU flag for thp freezing

On 04/21/2017 02:17 AM, Zi Yan wrote: > From: Naoya Horiguchi > > TTU_MIGRATION is used to convert pte into migration entry until thp split > completes. This behavior conflicts with thp migration added later patches, > so let's introduce a new TTU flag specifically for

Re: [PATCH v5 03/11] mm: thp: introduce separate TTU flag for thp freezing

On 04/21/2017 02:17 AM, Zi Yan wrote: > From: Naoya Horiguchi > > TTU_MIGRATION is used to convert pte into migration entry until thp split > completes. This behavior conflicts with thp migration added later patches, > so let's introduce a new TTU flag specifically for freezing. > >

linux-next: manual merge of the usb tree with the jc_docs tree

Hi all, Today's linux-next merge of the usb tree got a conflict in: Documentation/media/v4l-drivers/philips.rst between commit: 9b06f754133c ("convert philips.txt to ReST and add to media docs") from the jc_docs tree and commit: 21470e32ca7f ("usb: fix some references for

linux-next: manual merge of the usb tree with the jc_docs tree

Hi all, Today's linux-next merge of the usb tree got a conflict in: Documentation/media/v4l-drivers/philips.rst between commit: 9b06f754133c ("convert philips.txt to ReST and add to media docs") from the jc_docs tree and commit: 21470e32ca7f ("usb: fix some references for

Re: powerpc KVM build break in linux-next (was Re: [PATCH tip/core/rcu 40/40] srcu: Parallelize callback handling)

On Fri, Apr 21, 2017 at 11:42:01AM +1000, Michael Ellerman wrote: > "Paul E. McKenney" writes: > > On Thu, Apr 20, 2017 at 05:28:32PM +0200, Paolo Bonzini wrote: > >> On 20/04/2017 05:40, Michael Ellerman wrote: > >> > "Paul E. McKenney"

Re: powerpc KVM build break in linux-next (was Re: [PATCH tip/core/rcu 40/40] srcu: Parallelize callback handling)

On Fri, Apr 21, 2017 at 11:42:01AM +1000, Michael Ellerman wrote: > "Paul E. McKenney" writes: > > On Thu, Apr 20, 2017 at 05:28:32PM +0200, Paolo Bonzini wrote: > >> On 20/04/2017 05:40, Michael Ellerman wrote: > >> > "Paul E. McKenney" writes: > >> > > >> > This change seems to have had the

Re: [PATCH 1/3] dt-bindings: mt8173: Fix mdp device tree

On Wed, 2017-04-19 at 16:35 -0500, Rob Herring wrote: > On Thu, Apr 13, 2017 at 03:33:05PM +0800, Minghsiu Tsai wrote: > > If the mdp_* nodes are under an mdp sub-node, their corresponding > > platform device does not automatically get its iommu assigned properly. > > > > Fix this by moving the

Re: [PATCH v5 02/11] mm: mempolicy: add queue_pages_node_check()

On 04/21/2017 02:17 AM, Zi Yan wrote: > From: Naoya Horiguchi > > Introduce a separate check routine related to MPOL_MF_INVERT flag. > This patch just does cleanup, no behavioral change. Can you please send it separately first, this should be debated and merged

Re: [PATCH 1/3] dt-bindings: mt8173: Fix mdp device tree

On Wed, 2017-04-19 at 16:35 -0500, Rob Herring wrote: > On Thu, Apr 13, 2017 at 03:33:05PM +0800, Minghsiu Tsai wrote: > > If the mdp_* nodes are under an mdp sub-node, their corresponding > > platform device does not automatically get its iommu assigned properly. > > > > Fix this by moving the

Re: [PATCH v5 02/11] mm: mempolicy: add queue_pages_node_check()

On 04/21/2017 02:17 AM, Zi Yan wrote: > From: Naoya Horiguchi > > Introduce a separate check routine related to MPOL_MF_INVERT flag. > This patch just does cleanup, no behavioral change. Can you please send it separately first, this should be debated and merged quickly and not hang on to the

[PATCH] staging : rtl8188eu : remove void function return

kernel coding style doesn't allow the return statement in void function. Signed-off-by: Surenderp --- Changes for v2: corrected subject line as suggested Changes for v3: modified from line as suggested by Greg KH placed a semicolon in label for fixing build error ---

[PATCH] staging : rtl8188eu : remove void function return

kernel coding style doesn't allow the return statement in void function. Signed-off-by: Surenderp --- Changes for v2: corrected subject line as suggested Changes for v3: modified from line as suggested by Greg KH placed a semicolon in label for fixing build error ---

Re: [PATCH v6 1/6] dt-bindings: power: supply: add AXP20X/AXP22X battery DT binding

On Thu, Apr 20, 2017 at 11:58 PM, Rob Herring wrote: > On Tue, Apr 18, 2017 at 09:34:16AM +0200, Quentin Schulz wrote: >> The X-Powers AXP20X and AXP22X PMICs can have a battery as power supply. >> >> This patch adds the DT binding documentation for the battery power >> supply

Re: [PATCH v6 1/6] dt-bindings: power: supply: add AXP20X/AXP22X battery DT binding

On Thu, Apr 20, 2017 at 11:58 PM, Rob Herring wrote: > On Tue, Apr 18, 2017 at 09:34:16AM +0200, Quentin Schulz wrote: >> The X-Powers AXP20X and AXP22X PMICs can have a battery as power supply. >> >> This patch adds the DT binding documentation for the battery power >> supply which gets various

[PATCH V5 1/4] arm64: dts: Add basic DT to support Spreadtrum's SP9860G

From: Orson Zhai SC9860G is a 8 cores of A53 SoC with 4G LTE support SoC from Spreadtrum. According to regular hierarchy of sprd dts, whale2.dtsi contains SoC peripherals IP nodes, sc9860.dtsi contains stuff related to ARM core stuff and sp9860g dts is for the board

[PATCH V5 1/4] arm64: dts: Add basic DT to support Spreadtrum's SP9860G

From: Orson Zhai SC9860G is a 8 cores of A53 SoC with 4G LTE support SoC from Spreadtrum. According to regular hierarchy of sprd dts, whale2.dtsi contains SoC peripherals IP nodes, sc9860.dtsi contains stuff related to ARM core stuff and sp9860g dts is for the board level. Signed-off-by: Orson

[PATCH 1/2] dax: prevent invalidation of mapped DAX entries

dax_invalidate_mapping_entry() currently removes DAX exceptional entries only if they are clean and unlocked. This is done via: invalidate_mapping_pages() invalidate_exceptional_entry() dax_invalidate_mapping_entry() However, for page cache pages removed in invalidate_mapping_pages()

[PATCH 1/2] dax: prevent invalidation of mapped DAX entries

dax_invalidate_mapping_entry() currently removes DAX exceptional entries only if they are clean and unlocked. This is done via: invalidate_mapping_pages() invalidate_exceptional_entry() dax_invalidate_mapping_entry() However, for page cache pages removed in invalidate_mapping_pages()

  1   2   3   4   5   6   7   8   9   10   >