Re: RFC: Revert move default dialect from CIFS to to SMB3

On Fri, 2017-09-01 at 20:56 -0700, Linus Torvalds wrote: > On Fri, Sep 1, 2017 at 7:16 PM, Steve French wrote: > > > > The default was SMB1 (CIFS) and was recently changed to SMB3. > > The dialect still can be overridden by specifying "vers=1.0" or "vers=2.1" > > etc. on

Re: RFC: Revert move default dialect from CIFS to to SMB3

On Fri, 2017-09-01 at 20:56 -0700, Linus Torvalds wrote: > On Fri, Sep 1, 2017 at 7:16 PM, Steve French wrote: > > > > The default was SMB1 (CIFS) and was recently changed to SMB3. > > The dialect still can be overridden by specifying "vers=1.0" or "vers=2.1" > > etc. on mount. > > > > We just

Linux 4.9.47

I'm announcing the release of the 4.9.47 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Linux 4.9.47

I'm announcing the release of the 4.9.47 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.9.47

diff --git a/Makefile b/Makefile index 846ef1b57a02..a0abbfc15a49 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 46 +SUBLEVEL = 47 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c index

Re: Linux 4.9.47

diff --git a/Makefile b/Makefile index 846ef1b57a02..a0abbfc15a49 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 46 +SUBLEVEL = 47 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c index

Re: Linux 4.4.86

diff --git a/Makefile b/Makefile index 0f3d843f42a7..1207bf6a0e7a 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 85 +SUBLEVEL = 86 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c index

Linux 4.4.86

I'm announcing the release of the 4.4.86 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.4.86

diff --git a/Makefile b/Makefile index 0f3d843f42a7..1207bf6a0e7a 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 85 +SUBLEVEL = 86 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c index

Linux 4.4.86

I'm announcing the release of the 4.4.86 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 3.18.69

diff --git a/Makefile b/Makefile index 0d7f1e91e910..49237a0442cd 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 18 -SUBLEVEL = 68 +SUBLEVEL = 69 EXTRAVERSION = NAME = Diseased Newt diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c index

Linux 3.18.69

I'm announcing the release of the 3.18.69 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web

Linux 3.18.69

I'm announcing the release of the 3.18.69 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web

Re: Linux 3.18.69

diff --git a/Makefile b/Makefile index 0d7f1e91e910..49237a0442cd 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 18 -SUBLEVEL = 68 +SUBLEVEL = 69 EXTRAVERSION = NAME = Diseased Newt diff --git a/arch/arm64/kernel/fpsimd.c b/arch/arm64/kernel/fpsimd.c index

Re: [RFC 0/4] mmc: sdhci-msm: Add CQE support for sdhci-msm

On 8/31/2017 2:09 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: Hi All, Please ignore the previous patch series from a wrong email address. Stupid gitconfig issue. Apologies for the spam. This is RFC patch series based on top of ulfh_mmc/cmdq branch which is based upon

Re: [RFC 0/4] mmc: sdhci-msm: Add CQE support for sdhci-msm

On 8/31/2017 2:09 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: Hi All, Please ignore the previous patch series from a wrong email address. Stupid gitconfig issue. Apologies for the spam. This is RFC patch series based on top of ulfh_mmc/cmdq branch which is based upon

Re: [RFC 4/4] mmc: sdhci-msm: Handle unexpected interrupt case on enabling legacy IRQs on CQE halt

On 8/31/2017 1:05 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: There is a case when enabling the legacy IRQs and halting CQE is resuling into a command response interrupt without any command in progress. This patch handles such case here. Error signature without this

Re: [RFC 4/4] mmc: sdhci-msm: Handle unexpected interrupt case on enabling legacy IRQs on CQE halt

On 8/31/2017 1:05 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: There is a case when enabling the legacy IRQs and halting CQE is resuling into a command response interrupt without any command in progress. This patch handles such case here. Error signature without this

Re: [RFC 3/4] mmc: sdhci-msm: Change the desc_sz on cqe_enable/disable.

On 8/31/2017 12:12 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: When CMDQ is halted the HW expects descriptor size to be same which is using in CMDQ mode. Thus adjust the desc_sz of sdhci accordingly. Without this patch below command gives ADMA error when CQE is enabled.

Re: [RFC 3/4] mmc: sdhci-msm: Change the desc_sz on cqe_enable/disable.

On 8/31/2017 12:12 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: When CMDQ is halted the HW expects descriptor size to be same which is using in CMDQ mode. Thus adjust the desc_sz of sdhci accordingly. Without this patch below command gives ADMA error when CQE is enabled.

Re: [RFC 2/4] mmc: sdhci-msm: Add CQHCI support for sdhci-msm

On 8/31/2017 12:55 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: This adds CQHCI support for sdhci-msm platforms. Signed-off-by: Ritesh Harjani --- .../devicetree/bindings/mmc/sdhci-msm.txt | 1 + drivers/mmc/host/Kconfig

Re: [RFC 2/4] mmc: sdhci-msm: Add CQHCI support for sdhci-msm

On 8/31/2017 12:55 PM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: This adds CQHCI support for sdhci-msm platforms. Signed-off-by: Ritesh Harjani --- .../devicetree/bindings/mmc/sdhci-msm.txt | 1 + drivers/mmc/host/Kconfig | 1 +

Re: [RFC 1/4] mmc: cqhci: Move CQHCI_ENABLE before setting TDLBA/TDLBAU

On 8/31/2017 11:31 AM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: Without this patch the CQHCI registers are getting reset again. Signed-off-by: Ritesh Harjani --- drivers/mmc/host/cqhci.c | 7 +++ 1 file changed, 3 insertions(+), 4

Re: [RFC 1/4] mmc: cqhci: Move CQHCI_ENABLE before setting TDLBA/TDLBAU

On 8/31/2017 11:31 AM, Adrian Hunter wrote: On 30/08/17 16:04, Ritesh Harjani wrote: Without this patch the CQHCI registers are getting reset again. Signed-off-by: Ritesh Harjani --- drivers/mmc/host/cqhci.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

Warnings from include/linux/gpio/consumer.h with CONFIG_GPIOLIB=n

Hi Linus, I think Sergei or someone else was mentioning that before a while ago, but when CONFIG_GPIOLIB=n most gpiod_* inline stubs have WARN_ON() that will scare people. What do you recommend doing for code that might be built with or without CONFIG_GPIOLIB, should we just encapsulate the part

Warnings from include/linux/gpio/consumer.h with CONFIG_GPIOLIB=n

Hi Linus, I think Sergei or someone else was mentioning that before a while ago, but when CONFIG_GPIOLIB=n most gpiod_* inline stubs have WARN_ON() that will scare people. What do you recommend doing for code that might be built with or without CONFIG_GPIOLIB, should we just encapsulate the part

Re: [PATCH 13/13] thermal/drivers/hisi: Remove mutex_lock in the code

On Wed, Aug 30, 2017 at 10:47:37AM +0200, Daniel Lezcano wrote: > The mutex is used to protect against writes in the configuration register. > > That happens at probe time, with no possible race yet. > > Then when the module is unloaded and at suspend/resume. > > When the module is unloaded, it

Re: [PATCH 13/13] thermal/drivers/hisi: Remove mutex_lock in the code

On Wed, Aug 30, 2017 at 10:47:37AM +0200, Daniel Lezcano wrote: > The mutex is used to protect against writes in the configuration register. > > That happens at probe time, with no possible race yet. > > Then when the module is unloaded and at suspend/resume. > > When the module is unloaded, it

Re: [PATCH] locking/refcounts, x86/asm: Use unique .text section for refcount exceptions

On Fri, 2017-09-01 at 13:22 -0700, Kees Cook wrote: > Using .text.unlikely for refcount exceptions isn't safe because gcc may > move entire functions into .text.unlikely (e.g. in6_dev_get()), which > would cause any uses of a protected refcount_t function to stay inline > with the function,

Re: [PATCH] locking/refcounts, x86/asm: Use unique .text section for refcount exceptions

On Fri, 2017-09-01 at 13:22 -0700, Kees Cook wrote: > Using .text.unlikely for refcount exceptions isn't safe because gcc may > move entire functions into .text.unlikely (e.g. in6_dev_get()), which > would cause any uses of a protected refcount_t function to stay inline > with the function,

Re: RFC: Revert move default dialect from CIFS to to SMB3

On Fri, Sep 1, 2017 at 7:16 PM, Steve French wrote: > > The default was SMB1 (CIFS) and was recently changed to SMB3. > The dialect still can be overridden by specifying "vers=1.0" or "vers=2.1" > etc. on mount. > > We just put together a patch to better explain the default

Re: RFC: Revert move default dialect from CIFS to to SMB3

On Fri, Sep 1, 2017 at 7:16 PM, Steve French wrote: > > The default was SMB1 (CIFS) and was recently changed to SMB3. > The dialect still can be overridden by specifying "vers=1.0" or "vers=2.1" > etc. on mount. > > We just put together a patch to better explain the default changes > (with

Re: [PATCH] ipv6: sr: Use ARRAY_SIZE macro

On Fri, 2017-09-01 at 18:35 -0700, David Miller wrote: > From: Thomas Meyer > Date: Thu, 31 Aug 2017 16:18:15 +0200 > > > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first > > candidates. > > Maybe a coccinelle can catch all of those. Umm: try

Re: [PATCH] ipv6: sr: Use ARRAY_SIZE macro

On Fri, 2017-09-01 at 18:35 -0700, David Miller wrote: > From: Thomas Meyer > Date: Thu, 31 Aug 2017 16:18:15 +0200 > > > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first > > candidates. > > Maybe a coccinelle can catch all of those. Umm: try

Re: [PATCH 11/13] thermal/drivers/hisi: Convert long to int

On Wed, Aug 30, 2017 at 10:47:35AM +0200, Daniel Lezcano wrote: > There is no point to specify the temperature as long variable, the int is > enough. > > Replace all long variables to int, so making the code consistent. > > Signed-off-by: Daniel Lezcano Reviewed-by:

Re: [PATCH 11/13] thermal/drivers/hisi: Convert long to int

On Wed, Aug 30, 2017 at 10:47:35AM +0200, Daniel Lezcano wrote: > There is no point to specify the temperature as long variable, the int is > enough. > > Replace all long variables to int, so making the code consistent. > > Signed-off-by: Daniel Lezcano Reviewed-by: Leo Yan > --- >

Re: tunnels: Don't apply GRO to multiple layers of encapsulation.

On Thu, Aug 31, 2017 at 6:58 AM, wrote: > [ resend due to mail problems at my end ] > > Hi Jesse, > > The backport of fac8e0f579695a3ecbc4d3cac369139d7f819971, > "tunnels: Don't apply GRO to multiple layers of encapsulation", > to linux-4.1.y seems to have missed a

Re: tunnels: Don't apply GRO to multiple layers of encapsulation.

On Thu, Aug 31, 2017 at 6:58 AM, wrote: > [ resend due to mail problems at my end ] > > Hi Jesse, > > The backport of fac8e0f579695a3ecbc4d3cac369139d7f819971, > "tunnels: Don't apply GRO to multiple layers of encapsulation", > to linux-4.1.y seems to have missed a line. > > The 4.1 commit is

Re: [PATCH net-next, 0/4] cleanups and fixes of channel settings

From: Haiyang Zhang Date: Fri, 1 Sep 2017 14:30:03 -0700 > This patch set cleans up some unused variables, unnecessary checks. > Also fixed some limit checking of channel number. Series applied.

Re: [PATCH net-next, 0/4] cleanups and fixes of channel settings

From: Haiyang Zhang Date: Fri, 1 Sep 2017 14:30:03 -0700 > This patch set cleans up some unused variables, unnecessary checks. > Also fixed some limit checking of channel number. Series applied.

Re: [PATCH 10/13] thermal/drivers/hisi: Rename and remove unused field

On Wed, Aug 30, 2017 at 10:47:34AM +0200, Daniel Lezcano wrote: > Rename the 'sensors' field to 'sensor' as we describe only one sensor. > Remove the 'sensor_temp' as it is no longer used. > > Signed-off-by: Daniel Lezcano Reviewed-by: Leo Yan

Re: [PATCH 10/13] thermal/drivers/hisi: Rename and remove unused field

On Wed, Aug 30, 2017 at 10:47:34AM +0200, Daniel Lezcano wrote: > Rename the 'sensors' field to 'sensor' as we describe only one sensor. > Remove the 'sensor_temp' as it is no longer used. > > Signed-off-by: Daniel Lezcano Reviewed-by: Leo Yan Tested-by: Leo Yan > --- >

Re: [PATCH 09/13] thermal/drivers/hisi: Remove costly sensor inspection

On Wed, Aug 30, 2017 at 10:47:33AM +0200, Daniel Lezcano wrote: > The sensor is all setup, bind, resetted, acked, etc... every single second. > > That was the way to workaround a problem with the interrupt bouncing again and > again. > > With the following changes, we fix all in one: > > - Do

Re: [PATCH 09/13] thermal/drivers/hisi: Remove costly sensor inspection

On Wed, Aug 30, 2017 at 10:47:33AM +0200, Daniel Lezcano wrote: > The sensor is all setup, bind, resetted, acked, etc... every single second. > > That was the way to workaround a problem with the interrupt bouncing again and > again. > > With the following changes, we fix all in one: > > - Do

Re: [RFC Part1 PATCH v3 16/17] X86/KVM: Provide support to create Guest and HV shared per-CPU variables

On Fri, Sep 1, 2017 at 3:52 PM, Brijesh Singh wrote: > Hi Boris, > > On 08/30/2017 12:46 PM, Borislav Petkov wrote: >> >> On Wed, Aug 30, 2017 at 11:18:42AM -0500, Brijesh Singh wrote: >>> >>> I was trying to avoid mixing early and no-early set_memory_decrypted() >>> but if

Re: [RFC Part1 PATCH v3 16/17] X86/KVM: Provide support to create Guest and HV shared per-CPU variables

On Fri, Sep 1, 2017 at 3:52 PM, Brijesh Singh wrote: > Hi Boris, > > On 08/30/2017 12:46 PM, Borislav Petkov wrote: >> >> On Wed, Aug 30, 2017 at 11:18:42AM -0500, Brijesh Singh wrote: >>> >>> I was trying to avoid mixing early and no-early set_memory_decrypted() >>> but if >>> feedback is: use

Re: [PATCH] locking/refcounts, x86/asm: Use unique .text section for refcount exceptions

On Fri, Sep 1, 2017 at 2:43 PM, Ard Biesheuvel wrote: > On 1 September 2017 at 21:22, Kees Cook wrote: >> Using .text.unlikely for refcount exceptions isn't safe because gcc may >> move entire functions into .text.unlikely (e.g. in6_dev_get()),

Re: [PATCH] locking/refcounts, x86/asm: Use unique .text section for refcount exceptions

On Fri, Sep 1, 2017 at 2:43 PM, Ard Biesheuvel wrote: > On 1 September 2017 at 21:22, Kees Cook wrote: >> Using .text.unlikely for refcount exceptions isn't safe because gcc may >> move entire functions into .text.unlikely (e.g. in6_dev_get()), which >> would cause any uses of a protected

Re: [PATCH 08/13] thermal/drivers/hisi: Fix configuration register setting

On Wed, Aug 30, 2017 at 10:47:32AM +0200, Daniel Lezcano wrote: > The TEMP0_CFG configuration register contains different field to set up the > temperature controller. However in the code, nothing prevents a setup to > overwrite the previous one: eg. writing the hdak value overwrites the sensor >

Re: [PATCH 08/13] thermal/drivers/hisi: Fix configuration register setting

On Wed, Aug 30, 2017 at 10:47:32AM +0200, Daniel Lezcano wrote: > The TEMP0_CFG configuration register contains different field to set up the > temperature controller. However in the code, nothing prevents a setup to > overwrite the previous one: eg. writing the hdak value overwrites the sensor >

Re: [PATCH 07/13] thermal/drivers/hisi: Encapsulate register writes into helpers

On Sat, Sep 02, 2017 at 10:09:15AM +0800, Leo Yan wrote: > On Wed, Aug 30, 2017 at 10:47:31AM +0200, Daniel Lezcano wrote: > > Hopefully, the function name can help to clarify the semantic of the > > operations > > when writing in the register. > > > > Signed-off-by: Daniel Lezcano

Re: [PATCH 07/13] thermal/drivers/hisi: Encapsulate register writes into helpers

On Sat, Sep 02, 2017 at 10:09:15AM +0800, Leo Yan wrote: > On Wed, Aug 30, 2017 at 10:47:31AM +0200, Daniel Lezcano wrote: > > Hopefully, the function name can help to clarify the semantic of the > > operations > > when writing in the register. > > > > Signed-off-by: Daniel Lezcano > > --- > >

Re: RFC: Revert move default dialect from CIFS to to SMB3

On Fri, Sep 1, 2017 at 2:45 PM, Linus Torvalds wrote: > On Fri, Sep 1, 2017 at 11:23 AM, L. A. Walsh wrote: >>Why be incompatible with the majority of Windows installations? >> I.e. If you really want to up security from 1.0 (not adverse

Re: RFC: Revert move default dialect from CIFS to to SMB3

On Fri, Sep 1, 2017 at 2:45 PM, Linus Torvalds wrote: > On Fri, Sep 1, 2017 at 11:23 AM, L. A. Walsh wrote: >>Why be incompatible with the majority of Windows installations? >> I.e. If you really want to up security from 1.0 (not adverse to that), >> then why not go to 2.1 as used by Win7?

Re: [PATCH v3 2/5] dt-bindings: input: Add document bindings for mtk-pmic-keys

On Thu, 2017-08-31 at 14:52 -0500, Rob Herring wrote: > On Fri, Aug 25, 2017 at 02:32:30PM +0800, Chen Zhong wrote: > > This patch adds the device tree binding documentation for the MediaTek > > pmic keys found on PMIC MT6397/MT6323. > > > > Signed-off-by: Chen Zhong > >

Re: [PATCH V5 0/4] Add Broadcom STB USB phy driver

On 08/25/2017 10:51 AM, Al Cooper wrote: > Add a new USB Phy driver for Broadcom STB SoCs. This driver > supports Broadcom STB ARM SoCs. This driver in > combination with the Broadcom STB ohci, ehci and xhci > drivers will enable USB1.1, USB2.0 and USB3.0 support. > This Phy driver also supports

Re: [PATCH v3 2/5] dt-bindings: input: Add document bindings for mtk-pmic-keys

On Thu, 2017-08-31 at 14:52 -0500, Rob Herring wrote: > On Fri, Aug 25, 2017 at 02:32:30PM +0800, Chen Zhong wrote: > > This patch adds the device tree binding documentation for the MediaTek > > pmic keys found on PMIC MT6397/MT6323. > > > > Signed-off-by: Chen Zhong > > --- > >

Re: [PATCH V5 0/4] Add Broadcom STB USB phy driver

On 08/25/2017 10:51 AM, Al Cooper wrote: > Add a new USB Phy driver for Broadcom STB SoCs. This driver > supports Broadcom STB ARM SoCs. This driver in > combination with the Broadcom STB ohci, ehci and xhci > drivers will enable USB1.1, USB2.0 and USB3.0 support. > This Phy driver also supports

Re: [PATCH V5 1/4] soc: brcmstb: Add Product ID and Family ID helper functions

On 08/25/2017 10:51 AM, Al Cooper wrote: > Signed-off-by: Al Cooper Acked-by: Florian Fainelli > --- > drivers/soc/bcm/brcmstb/common.c| 12 > include/linux/soc/brcmstb/brcmstb.h | 10 ++ > 2 files changed, 22 insertions(+)

Re: [PATCH V5 1/4] soc: brcmstb: Add Product ID and Family ID helper functions

On 08/25/2017 10:51 AM, Al Cooper wrote: > Signed-off-by: Al Cooper Acked-by: Florian Fainelli > --- > drivers/soc/bcm/brcmstb/common.c| 12 > include/linux/soc/brcmstb/brcmstb.h | 10 ++ > 2 files changed, 22 insertions(+) > > diff --git

Re: [PATCH 2/2] ARM: dts: Add the PWM node to Cygnus

On 08/31/2017 01:10 PM, Scott Branden wrote: > pwm node is correct. > > > On 17-08-31 11:54 AM, Eric Anholt wrote: >> This is connected up to the backlight on 911360_entphn, which we'll >> need for a panel driver. For now, leave the node disabled in the >> shared dtsi. >> >> Signed-off-by:

Re: [PATCH 2/2] ARM: dts: Add the PWM node to Cygnus

On 08/31/2017 01:10 PM, Scott Branden wrote: > pwm node is correct. > > > On 17-08-31 11:54 AM, Eric Anholt wrote: >> This is connected up to the backlight on 911360_entphn, which we'll >> need for a panel driver. For now, leave the node disabled in the >> shared dtsi. >> >> Signed-off-by:

Re: [PATCH 1/2] ARM: dts: Add the CLCD controller to Cygnus.

On 08/31/2017 01:16 PM, Scott Branden wrote: > Hi Eric, > > mode is correct, location in file needs to be moved. > > > On 17-08-31 11:54 AM, Eric Anholt wrote: >> This doesn't yet enable it on any particular platform, as we still >> need a panel driver for bcm911360_entphn. >> >>

Re: [PATCH 1/2] ARM: dts: Add the CLCD controller to Cygnus.

On 08/31/2017 01:16 PM, Scott Branden wrote: > Hi Eric, > > mode is correct, location in file needs to be moved. > > > On 17-08-31 11:54 AM, Eric Anholt wrote: >> This doesn't yet enable it on any particular platform, as we still >> need a panel driver for bcm911360_entphn. >> >>

Re: [PATCH 07/13] thermal/drivers/hisi: Encapsulate register writes into helpers

On Wed, Aug 30, 2017 at 10:47:31AM +0200, Daniel Lezcano wrote: > Hopefully, the function name can help to clarify the semantic of the > operations > when writing in the register. > > Signed-off-by: Daniel Lezcano > --- > drivers/thermal/hisi_thermal.c | 96 >

Re: [PATCH 07/13] thermal/drivers/hisi: Encapsulate register writes into helpers

On Wed, Aug 30, 2017 at 10:47:31AM +0200, Daniel Lezcano wrote: > Hopefully, the function name can help to clarify the semantic of the > operations > when writing in the register. > > Signed-off-by: Daniel Lezcano > --- > drivers/thermal/hisi_thermal.c | 96 >

Re: [PATCH 3/3] dmaengine: sun6i: Add support for Allwinner A64

On Samstag, 2. September 2017 00:32:50 CEST André Przywara wrote: > Hi, > > On 01/09/17 02:19, Stefan Bruens wrote: > > On Freitag, 1. September 2017 02:31:35 CEST Andre Przywara wrote: > >> Hi, > >> > >> On 31/08/17 00:36, Stefan Brüns wrote: > >>> The A64 SoC has the same dma engine as the H3

Re: [PATCH 3/3] dmaengine: sun6i: Add support for Allwinner A64

On Samstag, 2. September 2017 00:32:50 CEST André Przywara wrote: > Hi, > > On 01/09/17 02:19, Stefan Bruens wrote: > > On Freitag, 1. September 2017 02:31:35 CEST Andre Przywara wrote: > >> Hi, > >> > >> On 31/08/17 00:36, Stefan Brüns wrote: > >>> The A64 SoC has the same dma engine as the H3

Re: [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

hi brian, On 09/02/2017 08:47 AM, Brian Norris wrote: On Sat, Sep 02, 2017 at 07:52:37AM +0800, Jeffy Chen wrote: Currently we are using edev->dev drvdata to get rk3399-dmc data, but it would be inited to edev in devfreq_event_add_edev. So we need to clear the edev->dev drvdata before enabling

Re: [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

hi brian, On 09/02/2017 08:47 AM, Brian Norris wrote: On Sat, Sep 02, 2017 at 07:52:37AM +0800, Jeffy Chen wrote: Currently we are using edev->dev drvdata to get rk3399-dmc data, but it would be inited to edev in devfreq_event_add_edev. So we need to clear the edev->dev drvdata before enabling

Re: [PATCH] ipv6: sr: Use ARRAY_SIZE macro

From: Thomas Meyer Date: Thu, 31 Aug 2017 16:18:15 +0200 > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first > candidates. > Maybe a coccinelle can catch all of those. > > Signed-off-by: Thomas Meyer Applied, thanks.

Re: [PATCH] ipv6: sr: Use ARRAY_SIZE macro

From: Thomas Meyer Date: Thu, 31 Aug 2017 16:18:15 +0200 > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first > candidates. > Maybe a coccinelle can catch all of those. > > Signed-off-by: Thomas Meyer Applied, thanks.

Re: [PATCH][net-next] net: qualcomm: rmnet: remove unused variable priv

From: Colin King Date: Thu, 31 Aug 2017 15:07:27 +0100 > From: Colin Ian King > > priv is being assigned but is never used, so remove it. > > Cleans up clang build warning: > "warning: Value stored to 'priv' is never read" > > Fixes:

Re: [PATCH][net-next] net: qualcomm: rmnet: remove unused variable priv

From: Colin King Date: Thu, 31 Aug 2017 15:07:27 +0100 > From: Colin Ian King > > priv is being assigned but is never used, so remove it. > > Cleans up clang build warning: > "warning: Value stored to 'priv' is never read" > > Fixes: ceed73a2cf4a ("drivers: net: ethernet: qualcomm: rmnet:

Re: [PATCH] net: phy: bcm7xxx: make array bcm7xxx_suspend_cfg static, reduces object code size

From: Colin King Date: Thu, 31 Aug 2017 14:57:15 +0100 > From: Colin Ian King > > Don't populate the array bcm7xxx_suspend_cfg A on the stack, instead > make it static. Makes the object code smaller by over 300 bytes: > > Before: >text

Re: [PATCH] net: phy: bcm7xxx: make array bcm7xxx_suspend_cfg static, reduces object code size

From: Colin King Date: Thu, 31 Aug 2017 14:57:15 +0100 > From: Colin Ian King > > Don't populate the array bcm7xxx_suspend_cfg A on the stack, instead > make it static. Makes the object code smaller by over 300 bytes: > > Before: >text data bss dec hex filename >

Re: [PATCH net-next v6] net: stmmac: Delete dead code for MDIO registration

From: Romain Perier Date: Thu, 31 Aug 2017 15:53:03 +0200 > This code is no longer used, the logging function was changed by commit > fbca164776e4 ("net: stmmac: Use the right logging function in > stmmac_mdio_register"). > It was previously showing information

Re: [PATCH net-next v6] net: stmmac: Delete dead code for MDIO registration

From: Romain Perier Date: Thu, 31 Aug 2017 15:53:03 +0200 > This code is no longer used, the logging function was changed by commit > fbca164776e4 ("net: stmmac: Use the right logging function in > stmmac_mdio_register"). > It was previously showing information about the type of the IRQ, if

Re: [PATCH 23/25] ALSA/dummy: Replace tasklet with softirq hrtimer

On p 1 2017 20:58, Takashi Iwai wrote: >From 07d61ba2a1c0e06e914443225e194d99f2d8c58d Mon Sep 17 00:00:00 2001 From: Takashi Sakamoto Date: Fri, 1 Sep 2017 19:10:18 +0900 Subject: [PATCH] ALSA: dummy: avoid stall due to a call of hrtimer_cancel() on a callback of

Re: [PATCH 23/25] ALSA/dummy: Replace tasklet with softirq hrtimer

On p 1 2017 20:58, Takashi Iwai wrote: >From 07d61ba2a1c0e06e914443225e194d99f2d8c58d Mon Sep 17 00:00:00 2001 From: Takashi Sakamoto Date: Fri, 1 Sep 2017 19:10:18 +0900 Subject: [PATCH] ALSA: dummy: avoid stall due to a call of hrtimer_cancel() on a callback of hrtimer A call of

Re: [PATCH] f2fs: avoid needless inode updates

Please ignore this patch. Thanks, On 09/01, Jaegeuk Kim wrote: > If i_size wan't change at all, we don't need to write inode during fsync. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/f2fs.h | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff

Re: [PATCH] f2fs: avoid needless inode updates

Please ignore this patch. Thanks, On 09/01, Jaegeuk Kim wrote: > If i_size wan't change at all, we don't need to write inode during fsync. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/f2fs.h | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/fs/f2fs/f2fs.h

Re: [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

On Sat, Sep 02, 2017 at 07:52:37AM +0800, Jeffy Chen wrote: > Currently we are using edev->dev drvdata to get rk3399-dmc data, but > it would be inited to edev in devfreq_event_add_edev. > > So we need to clear the edev->dev drvdata before enabling dfi, to > prevent dfi from getting the wrong

Re: [PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

On Sat, Sep 02, 2017 at 07:52:37AM +0800, Jeffy Chen wrote: > Currently we are using edev->dev drvdata to get rk3399-dmc data, but > it would be inited to edev in devfreq_event_add_edev. > > So we need to clear the edev->dev drvdata before enabling dfi, to > prevent dfi from getting the wrong

Re: [PATCH 3/3] dmaengine: sun6i: Add support for Allwinner A64

On Samstag, 2. September 2017 00:32:50 CEST André Przywara wrote: > Hi, > > On 01/09/17 02:19, Stefan Bruens wrote: > > On Freitag, 1. September 2017 02:31:35 CEST Andre Przywara wrote: > >> Hi, > >> > >> On 31/08/17 00:36, Stefan Brüns wrote: [...] > > > > For these 3 properties it likely is a

Re: [PATCH 3/3] dmaengine: sun6i: Add support for Allwinner A64

On Samstag, 2. September 2017 00:32:50 CEST André Przywara wrote: > Hi, > > On 01/09/17 02:19, Stefan Bruens wrote: > > On Freitag, 1. September 2017 02:31:35 CEST Andre Przywara wrote: > >> Hi, > >> > >> On 31/08/17 00:36, Stefan Brüns wrote: [...] > > > > For these 3 properties it likely is a

Re: [PATCH] sched: reset sysctl_sched_time_avg to default when

Yep, that is the first place I considered to set the limit, but that would break KABI ? Thanks, Ethan On Fri, Sep 1, 2017 at 8:32 PM, Peter Zijlstra wrote: > On Fri, Sep 01, 2017 at 07:31:54PM +0800, Ethan Zhao wrote: >> System will hang if user set sysctl_sched_time_avg

Re: [PATCH] sched: reset sysctl_sched_time_avg to default when

Yep, that is the first place I considered to set the limit, but that would break KABI ? Thanks, Ethan On Fri, Sep 1, 2017 at 8:32 PM, Peter Zijlstra wrote: > On Fri, Sep 01, 2017 at 07:31:54PM +0800, Ethan Zhao wrote: >> System will hang if user set sysctl_sched_time_avg to 0 by >> >> [root@XXX

Re: [PATCH 00/12] x86/crypto: Fix RBP usage in several crypto .S files

Hi Josh, On Tue, Aug 29, 2017 at 01:05:33PM -0500, Josh Poimboeuf wrote: > Many of the x86 crypto functions use RBP as a temporary register. This > breaks frame pointer convention, and breaks stack traces when unwinding > from an interrupt in the crypto code. > > Convert most* of them to leave

Re: [PATCH 00/12] x86/crypto: Fix RBP usage in several crypto .S files

Hi Josh, On Tue, Aug 29, 2017 at 01:05:33PM -0500, Josh Poimboeuf wrote: > Many of the x86 crypto functions use RBP as a temporary register. This > breaks frame pointer convention, and breaks stack traces when unwinding > from an interrupt in the crypto code. > > Convert most* of them to leave

[PATCH] f2fs: avoid needless inode updates

If i_size wan't change at all, we don't need to write inode during fsync. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 4b993961d81d..0d76b572484a 100644 ---

[PATCH] f2fs: avoid needless inode updates

If i_size wan't change at all, we don't need to write inode during fsync. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 4b993961d81d..0d76b572484a 100644 --- a/fs/f2fs/f2fs.h +++

[GIT PULL] ARM: SoC fixes for 4.13

Hi Linus, Just a few final fixes for 4.13. See below for description. Please merge. Thanks, -Olof The following changes since commit 93a4c8355e0e448d83f31801b4c72f66e4360975: ARM: dts: exynos: add needs-hpd for Odroid-XU3/4 (2017-08-23 21:43:29 +0200) are available in the git repository

Re: [GIT PULL] ARM: at91: DT for 4.14#2

On Wed, Aug 30, 2017 at 06:39:05PM +0200, Alexandre Belloni wrote: > Hi Olof, > > As discussed, this replaces the previous pull request. The only change > is the fixed up SoB. > > The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: > > Linux v4.13-rc1 (2017-07-15

Re: [GIT PULL] ARM: at91: DT for 4.14#2

On Wed, Aug 30, 2017 at 06:39:05PM +0200, Alexandre Belloni wrote: > Hi Olof, > > As discussed, this replaces the previous pull request. The only change > is the fixed up SoB. > > The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: > > Linux v4.13-rc1 (2017-07-15

[GIT PULL] ARM: SoC fixes for 4.13

Hi Linus, Just a few final fixes for 4.13. See below for description. Please merge. Thanks, -Olof The following changes since commit 93a4c8355e0e448d83f31801b4c72f66e4360975: ARM: dts: exynos: add needs-hpd for Odroid-XU3/4 (2017-08-23 21:43:29 +0200) are available in the git repository

[PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

Currently we are using edev->dev drvdata to get rk3399-dmc data, but it would be inited to edev in devfreq_event_add_edev. So we need to clear the edev->dev drvdata before enabling dfi, to prevent dfi from getting the wrong rk3399-dmc data when the irq triggered too early. Signed-off-by: Jeffy

[PATCH] CHROMIUM: devfreq: rk3399: Clear edev->dev drvdata before enabling dfi

Currently we are using edev->dev drvdata to get rk3399-dmc data, but it would be inited to edev in devfreq_event_add_edev. So we need to clear the edev->dev drvdata before enabling dfi, to prevent dfi from getting the wrong rk3399-dmc data when the irq triggered too early. Signed-off-by: Jeffy

Re: [RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

On Fri, 2017-09-01 at 10:24 -0500, Rob Herring wrote: > On Thu, Aug 31, 2017 at 10:51 PM, Benjamin Herrenschmidt > wrote: > > This allow to (slowly) migrate those embedded platforms > > to of_platform_default_populate() > > > > Signed-off-by: Benjamin Herrenschmidt

Re: [RFC/PATCH] drivers/of/platform: Add powerpc 4xx embedded busses to default list

On Fri, 2017-09-01 at 10:24 -0500, Rob Herring wrote: > On Thu, Aug 31, 2017 at 10:51 PM, Benjamin Herrenschmidt > wrote: > > This allow to (slowly) migrate those embedded platforms > > to of_platform_default_populate() > > > > Signed-off-by: Benjamin Herrenschmidt > > --- > > > > I'm here to

  1   2   3   4   5   6   7   8   9   10   >