Re: [PATCH] iio: adc: Add support for TI ADC1x8s102

On Thu, Apr 27, 2017 at 07:01:07AM +0100, Jonathan Cameron wrote: > Somewhat of a pain to basically use a random value as the default going > forward. Presumably this isn't the first ever ACPI table to need to > tell use about a reference voltage... > Mark, seen anything similar? > I see

Re: [PATCH] iio: adc: Add support for TI ADC1x8s102

On Thu, Apr 27, 2017 at 07:01:07AM +0100, Jonathan Cameron wrote: > Somewhat of a pain to basically use a random value as the default going > forward. Presumably this isn't the first ever ACPI table to need to > tell use about a reference voltage... > Mark, seen anything similar? > I see

[PATCH 3/5] clk: mvebu: ap806: introduce a new binding

As for cp110, the initial intent when the binding of the ap806 system controller was to have one flat node. The idea being that what is currently a clock-only driver in drivers would become a MFD driver, exposing the clock, GPIO and pinctrl functionality. However, after taking a step back, this

[PATCH 3/5] clk: mvebu: ap806: introduce a new binding

As for cp110, the initial intent when the binding of the ap806 system controller was to have one flat node. The idea being that what is currently a clock-only driver in drivers would become a MFD driver, exposing the clock, GPIO and pinctrl functionality. However, after taking a step back, this

[PATCH 5/5] arm64: dts: marvell: use new binding for the system controller on ap806

The new binding for the system controller on ap806 moved the clock into a subnode. This preliminary step will allow to add gpio and pinctrl subnodes Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT ---

[PATCH 2/5] clk: mvebu: ap806: do not depend anymore of the *-clock-output-names

As it was done for the cp110, this patch modifies the way the clock names are created. The name of each clock is now created by using its physical address as a prefix (as it was done for the platform device names). Thanks to this we have an automatic way to compute a unique name. Reviewed-by:

[PATCH 5/5] arm64: dts: marvell: use new binding for the system controller on ap806

The new binding for the system controller on ap806 moved the clock into a subnode. This preliminary step will allow to add gpio and pinctrl subnodes Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-ap806.dtsi | 19 +++ 1 file

[PATCH 2/5] clk: mvebu: ap806: do not depend anymore of the *-clock-output-names

As it was done for the cp110, this patch modifies the way the clock names are created. The name of each clock is now created by using its physical address as a prefix (as it was done for the platform device names). Thanks to this we have an automatic way to compute a unique name. Reviewed-by:

[PATCH 1/5] clk: mvebu: ap806: cosmetic improvement

Instead of using >dev all over the place, introduce a pointer variable for it. Signed-off-by: Gregory CLEMENT --- drivers/clk/mvebu/ap806-system-controller.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git

[PATCH 4/5] arm64: dts: marvell: remove clock-output-names on ap806

The clock-output-names of the ap806-system-controller node are not used anymore, so remove them. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-ap806.dtsi | 4 1

[PATCH 0/5] Improve ap806 clk support on Marvell Armada 7K/8K

Hi, This series modifies the device tree binding of the clock of the AP806 part that we find in the Marvell Armada 7K/8K SoCs. As for the CP110, we want to be able to ease the integration of new clocks without breaking the backward compatibility. It is done in patch 2. We also want to ease the

[PATCH 1/5] clk: mvebu: ap806: cosmetic improvement

Instead of using >dev all over the place, introduce a pointer variable for it. Signed-off-by: Gregory CLEMENT --- drivers/clk/mvebu/ap806-system-controller.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/drivers/clk/mvebu/ap806-system-controller.c

[PATCH 4/5] arm64: dts: marvell: remove clock-output-names on ap806

The clock-output-names of the ap806-system-controller node are not used anymore, so remove them. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-ap806.dtsi | 4 1 file changed, 4 deletions(-) diff --git

[PATCH 0/5] Improve ap806 clk support on Marvell Armada 7K/8K

Hi, This series modifies the device tree binding of the clock of the AP806 part that we find in the Marvell Armada 7K/8K SoCs. As for the CP110, we want to be able to ease the integration of new clocks without breaking the backward compatibility. It is done in patch 2. We also want to ease the

[PATCH 5/7] clk: mvebu: cp110: add sdio clock to cp-110 system controller

From: Konstantin Porotchkin This commit updates the CP110 system controller driver to add the definition for a missing clock. The SDIO clock is dedicated driving the SDHCI interface and its frequency is 400MHz (2/5 of PLL source clock). The SDIO interface should be bound to

[PATCH 5/7] clk: mvebu: cp110: add sdio clock to cp-110 system controller

From: Konstantin Porotchkin This commit updates the CP110 system controller driver to add the definition for a missing clock. The SDIO clock is dedicated driving the SDHCI interface and its frequency is 400MHz (2/5 of PLL source clock). The SDIO interface should be bound to this clock and not

[PATCH 4/7] clk: mvebu: cp110: introduce a new binding

The initial intent when the binding of the cp110 system controller was to have one flat node. The idea being that what is currently a clock-only driver in drivers would become a MFD driver, exposing the clock, GPIO and pinctrl functionality. However, after taking a step back, this would lead to a

[PATCH 6/7] arm64: dts: marvell: remove *-clock-output-names on cp110

The *-clock-output-names of the cp110-system-controller0 node are not used anymore, so remove them. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi |

[PATCH 4/7] clk: mvebu: cp110: introduce a new binding

The initial intent when the binding of the cp110 system controller was to have one flat node. The idea being that what is currently a clock-only driver in drivers would become a MFD driver, exposing the clock, GPIO and pinctrl functionality. However, after taking a step back, this would lead to a

[PATCH 6/7] arm64: dts: marvell: remove *-clock-output-names on cp110

The *-clock-output-names of the cp110-system-controller0 node are not used anymore, so remove them. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi | 13 +- arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi |

[PATCH 7/7] arm64: dts: marvell: use new binding for the system controller on cp110

The new binding for the system controller on cp110 moved the clock controller into a subnode. This preliminary step will allow to add gpio and pinctrl subnodes. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT

[PATCH 0/7] Improve cp110 clk support on Marvell Armada 7K/8K

Hi, We got more information about the clock controllers and the clock tree of the CP110 part that we find in the Marvell Armada 7K/8K SoCs. The clock tree needs to be fixed, indeed the GOP clock is only the clock for the GOIP and not for the SDIO, it is fixed in the first patch. The second

[PATCH 7/7] arm64: dts: marvell: use new binding for the system controller on cp110

The new binding for the system controller on cp110 moved the clock controller into a subnode. This preliminary step will allow to add gpio and pinctrl subnodes. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT --- arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi | 41

[PATCH 0/7] Improve cp110 clk support on Marvell Armada 7K/8K

Hi, We got more information about the clock controllers and the clock tree of the CP110 part that we find in the Marvell Armada 7K/8K SoCs. The clock tree needs to be fixed, indeed the GOP clock is only the clock for the GOIP and not for the SDIO, it is fixed in the first patch. The second

[PATCH 1/7] clk: mvebu: cp110 fix name of the GOP gate clock

Actually the GOP clock (bit 18) is not at all used for emmc but only for GOP: let's fix the name. Changing the name in the device tree is not an issue because the name itself is not used to reference the clock. Thanks to this the ABI remains backward compatible. Signed-off-by: Gregory CLEMENT

[PATCH 1/7] clk: mvebu: cp110 fix name of the GOP gate clock

Actually the GOP clock (bit 18) is not at all used for emmc but only for GOP: let's fix the name. Changing the name in the device tree is not an issue because the name itself is not used to reference the clock. Thanks to this the ABI remains backward compatible. Signed-off-by: Gregory CLEMENT

[PATCH 2/7] clk: mvebu: cp110: make failure labels more meaningful

In preparation to the addition of a new clock, rename the goto labels used to handle the failure cases using a name related to the failure cause. This will allow to insert additional failing cases without renaming all the labels. Reviewed-by: Thomas Petazzoni

[PATCH 3/7] clk: mvebu: cp110: do not depend anymore of the *-clock-output-names

Using the *-clock-output-names property was a convenient way to have a unique name for each clock even when there are multiple cp110 blocks as we can find on Armada 8K. However it has some drawbacks: the main one being a stronger link than necessary between the driver and the device tree. For

[PATCH 2/7] clk: mvebu: cp110: make failure labels more meaningful

In preparation to the addition of a new clock, rename the goto labels used to handle the failure cases using a name related to the failure cause. This will allow to insert additional failing cases without renaming all the labels. Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT ---

[PATCH 3/7] clk: mvebu: cp110: do not depend anymore of the *-clock-output-names

Using the *-clock-output-names property was a convenient way to have a unique name for each clock even when there are multiple cp110 blocks as we can find on Armada 8K. However it has some drawbacks: the main one being a stronger link than necessary between the driver and the device tree. For

Re: [PATCH v5 01/11] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

On 04/20/2017 01:47 PM, Zi Yan wrote: > pmd_present() checks _PAGE_PSE along with _PAGE_PRESENT to avoid > false negative return when it races with thp spilt > (during which _PAGE_PRESENT is temporary cleared.) I don't think that > dropping _PAGE_PSE check in pmd_present() works well because it

Re: [PATCH v5 01/11] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

On 04/20/2017 01:47 PM, Zi Yan wrote: > pmd_present() checks _PAGE_PSE along with _PAGE_PRESENT to avoid > false negative return when it races with thp spilt > (during which _PAGE_PRESENT is temporary cleared.) I don't think that > dropping _PAGE_PSE check in pmd_present() works well because it

Re: [PATCH 2/3] regulator: lp87565: Add support for lp87565 PMIC regulators

On 05/19/2017 07:42 AM, Keerthy wrote: > The regulators set consists of 4 BUCKs. The output > voltages are configurable and are meant to supply power to the > main processor and other components. The ramp delay is configurable > for all BUCKs. The BUCKs can be configured in single phase or >

Re: [PATCH] usb: Use _nort in usb_hcd_pci_remove

On Thu, 20 Apr 2017 14:00:27 -0400 Nate Dailey wrote: > A trip through usb_hcd_pci_remove produces: > > BUG: sleeping function called from invalid context at > kernel/locking/rtmutex.c:993 > in_atomic(): 0, irqs_disabled(): 1, pid: 4752, name: bash > INFO: lockdep

Re: [PATCH 2/3] regulator: lp87565: Add support for lp87565 PMIC regulators

On 05/19/2017 07:42 AM, Keerthy wrote: > The regulators set consists of 4 BUCKs. The output > voltages are configurable and are meant to supply power to the > main processor and other components. The ramp delay is configurable > for all BUCKs. The BUCKs can be configured in single phase or >

Re: [PATCH] usb: Use _nort in usb_hcd_pci_remove

On Thu, 20 Apr 2017 14:00:27 -0400 Nate Dailey wrote: > A trip through usb_hcd_pci_remove produces: > > BUG: sleeping function called from invalid context at > kernel/locking/rtmutex.c:993 > in_atomic(): 0, irqs_disabled(): 1, pid: 4752, name: bash > INFO: lockdep is turned off. > irq

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

On Sat 20-05-17 00:22:30, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Fri 19-05-17 22:02:44, Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > Any allocation failure during the #PF path will return with VM_FAULT_OOM > > > > which in turn results in pagefault_out_of_memory. This can happen

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

On Sat 20-05-17 00:22:30, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Fri 19-05-17 22:02:44, Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > Any allocation failure during the #PF path will return with VM_FAULT_OOM > > > > which in turn results in pagefault_out_of_memory. This can happen

[PATCH 04/10] xen: remove non-pv test from arch/x86/xen/irq.c

As arch/x86/xen/irq.c is used for pv-guests only, there is no need to have a test targeting a HVM guest in it. Remove it. Signed-off-by: Juergen Gross --- arch/x86/xen/irq.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/arch/x86/xen/irq.c

[PATCH 04/10] xen: remove non-pv test from arch/x86/xen/irq.c

As arch/x86/xen/irq.c is used for pv-guests only, there is no need to have a test targeting a HVM guest in it. Remove it. Signed-off-by: Juergen Gross --- arch/x86/xen/irq.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/arch/x86/xen/irq.c b/arch/x86/xen/irq.c index

[PATCH 00/10] paravirt: make amount of paravirtualization configurable

Today paravirtualization is a all-or-nothing game: either a kernel is compiled with no paravirtualization support at all, or it is supporting paravirtualized environments like Xen pv-guests or lguest additionally to some paravirtualized tuning for KVM, Hyperv, VMWare or Xen HVM-guests. As support

[PATCH 00/10] paravirt: make amount of paravirtualization configurable

Today paravirtualization is a all-or-nothing game: either a kernel is compiled with no paravirtualization support at all, or it is supporting paravirtualized environments like Xen pv-guests or lguest additionally to some paravirtualized tuning for KVM, Hyperv, VMWare or Xen HVM-guests. As support

[PATCH 03/10] xen: move interrupt handling for pv guests under CONFIG_XEN_PV umbrella

There is no need to include pv-guest only object files in a kernel not configured to support those. Move Xen's irq.o, xen-asm*.o and pv parts of entry_*.o into CONFIG_XEN_PV sections. Signed-off-by: Juergen Gross --- arch/x86/entry/entry_32.S | 4 +++- arch/x86/entry/entry_64.S

[PATCH 02/10] paravirt: remove unused function paravirt_disable_iospace()

paravirt_disable_iospace() isn't used anywhere. Remove it. Signed-off-by: Juergen Gross --- arch/x86/include/asm/paravirt_types.h | 2 -- arch/x86/kernel/paravirt.c| 19 --- 2 files changed, 21 deletions(-) diff --git

[PATCH 03/10] xen: move interrupt handling for pv guests under CONFIG_XEN_PV umbrella

There is no need to include pv-guest only object files in a kernel not configured to support those. Move Xen's irq.o, xen-asm*.o and pv parts of entry_*.o into CONFIG_XEN_PV sections. Signed-off-by: Juergen Gross --- arch/x86/entry/entry_32.S | 4 +++- arch/x86/entry/entry_64.S | 6 --

[PATCH 02/10] paravirt: remove unused function paravirt_disable_iospace()

paravirt_disable_iospace() isn't used anywhere. Remove it. Signed-off-by: Juergen Gross --- arch/x86/include/asm/paravirt_types.h | 2 -- arch/x86/kernel/paravirt.c| 19 --- 2 files changed, 21 deletions(-) diff --git a/arch/x86/include/asm/paravirt_types.h

[PATCH 06/10] paravirt: split pv_cpu_ops for support of PARAVIRT_FULL

Move functions needed for fully paravirtualized guests only into a new structure pvfull_cpu_ops in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. Signed-off-by: Juergen Gross --- arch/x86/entry/entry_64.S | 4 +-

[PATCH 06/10] paravirt: split pv_cpu_ops for support of PARAVIRT_FULL

Move functions needed for fully paravirtualized guests only into a new structure pvfull_cpu_ops in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. Signed-off-by: Juergen Gross --- arch/x86/entry/entry_64.S | 4 +-

[PATCH 3/3] f2fs: wait discard IO completion without cmd_lock held

From: Chao Yu Wait discard IO completion outside cmd_lock to avoid long latency of holding cmd_lock in IO busy scenario. Signed-off-by: Chao Yu --- fs/f2fs/segment.c | 23 --- 1 file changed, 20 insertions(+), 3 deletions(-) diff

[PATCH 3/3] f2fs: wait discard IO completion without cmd_lock held

From: Chao Yu Wait discard IO completion outside cmd_lock to avoid long latency of holding cmd_lock in IO busy scenario. Signed-off-by: Chao Yu --- fs/f2fs/segment.c | 23 --- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/segment.c

Re: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure

On Thu, May 18, 2017 at 10:34:34AM +0200, Florian Weimer wrote: > On 05/18/2017 10:31 AM, Peter Zijlstra wrote: > > But it does that after building the tst-robustpi8 thing, so I seem to > > have all I need here. > > Great, have fun figuring out what's going on. :-/ Please test the below, it

Re: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure

On Thu, May 18, 2017 at 10:34:34AM +0200, Florian Weimer wrote: > On 05/18/2017 10:31 AM, Peter Zijlstra wrote: > > But it does that after building the tst-robustpi8 thing, so I seem to > > have all I need here. > > Great, have fun figuring out what's going on. :-/ Please test the below, it

[PATCH 07/10] paravirt: split pv_irq_ops for support of PARAVIRT_FULL

Move functions needed for fully paravirtualized guests only into a new structure pvfull_irq_ops in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. Signed-off-by: Juergen Gross --- arch/x86/include/asm/irqflags.h| 44

[PATCH 2/3] f2fs: wake up all waiters in f2fs_submit_discard_endio

From: Chao Yu There could be more than one waiter waiting discard IO completion, so we need use complete_all() instead of complete() in f2fs_submit_discard_endio to avoid hungtask. Fixes: ec9895add2c5 ("f2fs: don't hold cmd_lock during waiting discard command") Cc:

[PATCH 1/3] f2fs: show more info if fail to issue discard

From: Chao Yu Signed-off-by: Chao Yu --- fs/f2fs/segment.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c index a29919330e27..d310b82caef1 100644 --- a/fs/f2fs/segment.c +++ b/fs/f2fs/segment.c

[PATCH 05/10] paravirt: add new PARAVIRT_FULL config item

Add a new config item PARAVIRT_FULL. It will be used to guard the pv_*_ops functions used by fully paravirtualized guests (Xen pv-guests and lguest) only. Kernels not meant to support those guest types will be able to use many operations without paravirt abstraction while still supporting all the

[PATCH 07/10] paravirt: split pv_irq_ops for support of PARAVIRT_FULL

Move functions needed for fully paravirtualized guests only into a new structure pvfull_irq_ops in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. Signed-off-by: Juergen Gross --- arch/x86/include/asm/irqflags.h| 44

[PATCH 2/3] f2fs: wake up all waiters in f2fs_submit_discard_endio

From: Chao Yu There could be more than one waiter waiting discard IO completion, so we need use complete_all() instead of complete() in f2fs_submit_discard_endio to avoid hungtask. Fixes: ec9895add2c5 ("f2fs: don't hold cmd_lock during waiting discard command") Cc: Signed-off-by: Chao Yu ---

[PATCH 1/3] f2fs: show more info if fail to issue discard

From: Chao Yu Signed-off-by: Chao Yu --- fs/f2fs/segment.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c index a29919330e27..d310b82caef1 100644 --- a/fs/f2fs/segment.c +++ b/fs/f2fs/segment.c @@ -740,7 +740,8 @@ static void

[PATCH 05/10] paravirt: add new PARAVIRT_FULL config item

Add a new config item PARAVIRT_FULL. It will be used to guard the pv_*_ops functions used by fully paravirtualized guests (Xen pv-guests and lguest) only. Kernels not meant to support those guest types will be able to use many operations without paravirt abstraction while still supporting all the

[PATCH 10/10] paravirt: merge pv_ops_* structures into one

As there are now only very few pvops functions left when CONFIG_PARAVIRT_FULL isn't set, merge the related structures into one named "pv_ops". Signed-off-by: Juergen Gross --- arch/x86/include/asm/paravirt.h | 32

[PATCH 09/10] paravirt: split pv_info for support of PARAVIRT_FULL

Move members needed for fully paravirtualized guests only into a new structure pvfull_info in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. Signed-off-by: Juergen Gross --- arch/x86/boot/compressed/misc.h | 1 +

[PATCH 10/10] paravirt: merge pv_ops_* structures into one

As there are now only very few pvops functions left when CONFIG_PARAVIRT_FULL isn't set, merge the related structures into one named "pv_ops". Signed-off-by: Juergen Gross --- arch/x86/include/asm/paravirt.h | 32 arch/x86/include/asm/paravirt_types.h | 27

[PATCH 09/10] paravirt: split pv_info for support of PARAVIRT_FULL

Move members needed for fully paravirtualized guests only into a new structure pvfull_info in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. Signed-off-by: Juergen Gross --- arch/x86/boot/compressed/misc.h | 1 +

[PATCH 01/10] x86: remove stale prototype from arch/x86/include/asm/pgalloc.h

paravirt_alloc_pmd_clone() doesn't exist anywhere. Remove its prototype. Signed-off-by: Juergen Gross --- arch/x86/include/asm/pgalloc.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/x86/include/asm/pgalloc.h b/arch/x86/include/asm/pgalloc.h index

[PATCH 08/10] paravirt: split pv_mmu_ops for support of PARAVIRT_FULL

Move functions needed for fully paravirtualized guests only into a new structure pvfull_mmu_ops in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. .flush_tlb_others is left in pv_mmu_ops as hyperv support will use it soon. Signed-off-by: Juergen Gross

[PATCH 01/10] x86: remove stale prototype from arch/x86/include/asm/pgalloc.h

paravirt_alloc_pmd_clone() doesn't exist anywhere. Remove its prototype. Signed-off-by: Juergen Gross --- arch/x86/include/asm/pgalloc.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/x86/include/asm/pgalloc.h b/arch/x86/include/asm/pgalloc.h index b2d0cd8288aa..71de65bb1791 100644

[PATCH 08/10] paravirt: split pv_mmu_ops for support of PARAVIRT_FULL

Move functions needed for fully paravirtualized guests only into a new structure pvfull_mmu_ops in paravirt_types_full.h, paravirt_full.h and the associated vector into paravirt_full.c. .flush_tlb_others is left in pv_mmu_ops as hyperv support will use it soon. Signed-off-by: Juergen Gross ---

Re: [PATCH 4/4] arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite

Hi Michael, >> diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c >> index 2b33cfa..f75e512 100644 >> --- a/arch/powerpc/kernel/time.c >> +++ b/arch/powerpc/kernel/time.c >> @@ -738,12 +738,28 @@ static int __init get_freq(char *name, int cells, >> unsigned long *val) >> >>

Re: [PATCH 4/4] arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite

Hi Michael, >> diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c >> index 2b33cfa..f75e512 100644 >> --- a/arch/powerpc/kernel/time.c >> +++ b/arch/powerpc/kernel/time.c >> @@ -738,12 +738,28 @@ static int __init get_freq(char *name, int cells, >> unsigned long *val) >> >>

Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

On Mon, May 15, 2017 at 10:53 AM, Alex Williamson wrote: > On Mon, 15 May 2017 08:19:28 + > "Cheng, Collins" wrote: > >> Hi Williamson, >> >> We cannot assume BIOS supports SR-IOV, actually only newer server >> motherboard BIOS supports

Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

On Mon, May 15, 2017 at 10:53 AM, Alex Williamson wrote: > On Mon, 15 May 2017 08:19:28 + > "Cheng, Collins" wrote: > >> Hi Williamson, >> >> We cannot assume BIOS supports SR-IOV, actually only newer server >> motherboard BIOS supports SR-IOV. Normal desktop motherboard BIOS or older >>

Re: [PATCH] input: move gpio mouse to managed api

On 19/05/2017 17:35, Bram Vlerick wrote: > Signed-off-by: Bram Vlerick > --- > drivers/input/mouse/gpio_mouse.c | 10 ++ > 1 file changed, 2 insertions(+), 8 deletions(-) > > diff --git a/drivers/input/mouse/gpio_mouse.c > b/drivers/input/mouse/gpio_mouse.c > index

Re: [PATCH] input: move gpio mouse to managed api

On 19/05/2017 17:35, Bram Vlerick wrote: > Signed-off-by: Bram Vlerick > --- > drivers/input/mouse/gpio_mouse.c | 10 ++ > 1 file changed, 2 insertions(+), 8 deletions(-) > > diff --git a/drivers/input/mouse/gpio_mouse.c > b/drivers/input/mouse/gpio_mouse.c > index

Re: [PATCH 1/3] mfd: lp87565: Add lp87565 PMIC support

On 05/19/2017 07:42 AM, Keerthy wrote: > The LP87565 chip is a power management IC for Portable Navigation Systems > and Tablet Computing devices. It contains the following components: > > - Configurable Bucks(Single and multi-phase). > - Configurable General Purpose Output

Re: [PATCH 1/3] mfd: lp87565: Add lp87565 PMIC support

On 05/19/2017 07:42 AM, Keerthy wrote: > The LP87565 chip is a power management IC for Portable Navigation Systems > and Tablet Computing devices. It contains the following components: > > - Configurable Bucks(Single and multi-phase). > - Configurable General Purpose Output

Re: [PATCH] selinux: Mark array 'labeling_behaviors' as __maybe_unused

On Fri, 2017-05-19 at 11:09 -0400, Paul Moore wrote: > On Thu, May 18, 2017 at 3:07 PM, Matthias Kaehlcke > wrote: > > The array is only referenced in an ARRAY_SIZE() statement. Adding > > the > > attribute fixes the following warning when building with clang: > > > >

Re: [PATCH] selinux: Mark array 'labeling_behaviors' as __maybe_unused

On Fri, 2017-05-19 at 11:09 -0400, Paul Moore wrote: > On Thu, May 18, 2017 at 3:07 PM, Matthias Kaehlcke > wrote: > > The array is only referenced in an ARRAY_SIZE() statement. Adding > > the > > attribute fixes the following warning when building with clang: > > > >

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

On Fri, May 19, 2017 at 05:08:02AM +0200, Luis R. Rodriguez wrote: > On Fri, May 19, 2017 at 02:44:14AM +0200, Luis R. Rodriguez wrote: > > On Wed, May 17, 2017 at 10:53:06AM -0700, Kees Cook wrote: > > > On Wed, May 17, 2017 at 9:40 AM, Luis R. Rodriguez > > > wrote: > > > >

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

On Fri, May 19, 2017 at 05:08:02AM +0200, Luis R. Rodriguez wrote: > On Fri, May 19, 2017 at 02:44:14AM +0200, Luis R. Rodriguez wrote: > > On Wed, May 17, 2017 at 10:53:06AM -0700, Kees Cook wrote: > > > On Wed, May 17, 2017 at 9:40 AM, Luis R. Rodriguez > > > wrote: > > > > Yes, but I had

[PATCH v2 2/2] f2fs: introduce io_list for serialize data/node IOs

From: Chao Yu Serialize data/node IOs by using fifo list instead of mutex lock, it will help to enhance concurrency of f2fs, meanwhile keeping LFS IO semantics. Signed-off-by: Chao Yu --- v2: - rebase to last dev-test branch. fs/f2fs/checkpoint.c | 1

[PATCH v2 2/2] f2fs: introduce io_list for serialize data/node IOs

From: Chao Yu Serialize data/node IOs by using fifo list instead of mutex lock, it will help to enhance concurrency of f2fs, meanwhile keeping LFS IO semantics. Signed-off-by: Chao Yu --- v2: - rebase to last dev-test branch. fs/f2fs/checkpoint.c | 1 + fs/f2fs/data.c | 24

[PATCH v2 1/2] f2fs: split wio_mutex

From: Chao Yu Split wio_mutex to adjust different temperature bio cache. Signed-off-by: Chao Yu --- v2: - rebase to last dev-test branch. fs/f2fs/f2fs.h| 3 ++- fs/f2fs/segment.c | 4 ++-- fs/f2fs/super.c | 7 --- 3 files changed, 8

[PATCH v2 1/2] f2fs: split wio_mutex

From: Chao Yu Split wio_mutex to adjust different temperature bio cache. Signed-off-by: Chao Yu --- v2: - rebase to last dev-test branch. fs/f2fs/f2fs.h| 3 ++- fs/f2fs/segment.c | 4 ++-- fs/f2fs/super.c | 7 --- 3 files changed, 8 insertions(+), 6 deletions(-) diff --git

[PATCH] input: move gpio mouse to managed api

Signed-off-by: Bram Vlerick --- drivers/input/mouse/gpio_mouse.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/drivers/input/mouse/gpio_mouse.c b/drivers/input/mouse/gpio_mouse.c index ced07391304b..7d56fd5173bc 100644 ---

[PATCH] input: move gpio mouse to managed api

Signed-off-by: Bram Vlerick --- drivers/input/mouse/gpio_mouse.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/drivers/input/mouse/gpio_mouse.c b/drivers/input/mouse/gpio_mouse.c index ced07391304b..7d56fd5173bc 100644 --- a/drivers/input/mouse/gpio_mouse.c +++

Re: [PATCH] block: partitions: mac: Mark mac_fix_string() as __maybe_unused

On 05/18/2017 07:24 PM, Matthias Kaehlcke wrote: > The function is only used when CONFIG_PPC_PMAC=y. Adding the attribute > fixes the following warning when building with clang: > > block/partitions/mac.c:22:20: error: unused function 'mac_fix_string' > [-Werror,-Wunused-function] > >

Re: [PATCH] block: partitions: mac: Mark mac_fix_string() as __maybe_unused

On 05/18/2017 07:24 PM, Matthias Kaehlcke wrote: > The function is only used when CONFIG_PPC_PMAC=y. Adding the attribute > fixes the following warning when building with clang: > > block/partitions/mac.c:22:20: error: unused function 'mac_fix_string' > [-Werror,-Wunused-function] > >

Re: [PATCH 3/3] EDAC: mv64x60: replace in_le32/out_le32 with ioread32/iowrite32

On Fri, May 19, 2017 at 4:01 PM, David Laight wrote: > From: Arnd Bergmann >> Sent: 17 May 2017 22:40 >> >> On Wed, May 17, 2017 at 11:16 PM, Chris Packham >> wrote: >> > On 18/05/17 06:18, Borislav Petkov wrote: >> > One thing I would

Re: [PATCH 3/3] EDAC: mv64x60: replace in_le32/out_le32 with ioread32/iowrite32

On Fri, May 19, 2017 at 4:01 PM, David Laight wrote: > From: Arnd Bergmann >> Sent: 17 May 2017 22:40 >> >> On Wed, May 17, 2017 at 11:16 PM, Chris Packham >> wrote: >> > On 18/05/17 06:18, Borislav Petkov wrote: >> > One thing I would like confirmation on is is in_le32 -> ioread32 the >> >

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

Michal Hocko wrote: > On Fri 19-05-17 22:02:44, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > Any allocation failure during the #PF path will return with VM_FAULT_OOM > > > which in turn results in pagefault_out_of_memory. This can happen for > > > 2 different reasons. a) Memcg is out of

Re: [RFC PATCH 2/2] mm, oom: do not trigger out_of_memory from the #PF

Michal Hocko wrote: > On Fri 19-05-17 22:02:44, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > Any allocation failure during the #PF path will return with VM_FAULT_OOM > > > which in turn results in pagefault_out_of_memory. This can happen for > > > 2 different reasons. a) Memcg is out of

Re: [PATCH 4/4] Hyper-V vPCI: use vPCI protocol version 1.2

On Fri, 19 May 2017 14:27:01 +0300 Dan Carpenter wrote: > > /* > > + * HV_VP_SET available > > + */ > > +#define HV_X64_EX_PROCESSOR_MASKS_RECOMMENDED (1 << 11) > > Use BIT(11). I thought checkpatch.pl complains about this but I guess > that's only with the

Re: [PATCH 4/4] Hyper-V vPCI: use vPCI protocol version 1.2

On Fri, 19 May 2017 14:27:01 +0300 Dan Carpenter wrote: > > /* > > + * HV_VP_SET available > > + */ > > +#define HV_X64_EX_PROCESSOR_MASKS_RECOMMENDED (1 << 11) > > Use BIT(11). I thought checkpatch.pl complains about this but I guess > that's only with the --strict option. Since all

Re: [copyleft-next] Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

On Thu, May 18, 2017 at 04:29:23PM -0700, Luis R. Rodriguez wrote: > > The article I had referred to indicates how there are actually > *several* "or" clauses, and ambiguity between what they might mean. > Hence my surprise attorneys would exist who choose to green light all > code with a magical

Re: [copyleft-next] Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

On Thu, May 18, 2017 at 04:29:23PM -0700, Luis R. Rodriguez wrote: > > The article I had referred to indicates how there are actually > *several* "or" clauses, and ambiguity between what they might mean. > Hence my surprise attorneys would exist who choose to green light all > code with a magical

[PATCH v2] KVM: x86: Avoid guest page table walk when gpa_available is set

From: Brijesh Singh On AMD hardware when a guest causes a NPF which requires emulation, the vcpu->arch.gpa_available flag is set to indicate that cr2 contains a valid GPA. Currently, emulator_read_write_onepage() makes use of gpa_available flag to avoid a guest page walk

[PATCH v2] KVM: x86: Avoid guest page table walk when gpa_available is set

From: Brijesh Singh On AMD hardware when a guest causes a NPF which requires emulation, the vcpu->arch.gpa_available flag is set to indicate that cr2 contains a valid GPA. Currently, emulator_read_write_onepage() makes use of gpa_available flag to avoid a guest page walk for a known MMIO

Re: [PATCH] selinux: Mark array 'labeling_behaviors' as __maybe_unused

On Thu, May 18, 2017 at 3:07 PM, Matthias Kaehlcke wrote: > The array is only referenced in an ARRAY_SIZE() statement. Adding the > attribute fixes the following warning when building with clang: > > security/selinux/hooks.c:338:20: error: variable 'labeling_behaviors' > is

Re: [copyleft-next] Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

On Fri, May 19, 2017 at 12:31:50PM +0100, Alan Cox wrote: > > I really cannot see how you might have an attorney who wants ink on > > 2A but not 1A. > > I really cannot see how you might have an attorney who wants ink on > > 2B but not 1B. > > Because their job is to protect their whomsoever they

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