[PATCH] iio: multiplexer: check memory allocation failure

Check memory allocation failures and return -ENOMEM in such cases, as already done few lines above for another memory allocation. This avoids NULL pointers dereference. Signed-off-by: Christophe JAILLET --- drivers/iio/multiplexer/iio-mux.c | 6 ++ 1 file

[PATCH] iio: multiplexer: check memory allocation failure

Check memory allocation failures and return -ENOMEM in such cases, as already done few lines above for another memory allocation. This avoids NULL pointers dereference. Signed-off-by: Christophe JAILLET --- drivers/iio/multiplexer/iio-mux.c | 6 ++ 1 file changed, 6 insertions(+) diff

[PATCH v3 net-next 1/1] hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

Hyper-V Sockets (hv_sock) supplies a byte-stream based communication mechanism between the host and the guest. It uses VMBus ringbuffer as the transportation layer. With hv_sock, applications between the host (Windows 10, Windows Server 2016 or newer) and the guest can talk with each other using

[PATCH v3 net-next 1/1] hv_sock: implements Hyper-V transport for Virtual Sockets (AF_VSOCK)

Hyper-V Sockets (hv_sock) supplies a byte-stream based communication mechanism between the host and the guest. It uses VMBus ringbuffer as the transportation layer. With hv_sock, applications between the host (Windows 10, Windows Server 2016 or newer) and the guest can talk with each other using

Re: [RFC PATCH] treewide: remove GFP_TEMPORARY allocation flag

On Fri, Aug 25 2017, Pavel Machek wrote: > On Fri 2017-08-25 10:04:42, Michal Hocko wrote: >> On Fri 25-08-17 09:28:19, Pavel Machek wrote: >> > On Fri 2017-08-25 08:35:46, Michal Hocko wrote: >> > > On Wed 23-08-17 19:57:09, Pavel Machek wrote: >> [...] >> > > > Dunno. < 1msec probably is

Re: [RFC PATCH] treewide: remove GFP_TEMPORARY allocation flag

On Fri, Aug 25 2017, Pavel Machek wrote: > On Fri 2017-08-25 10:04:42, Michal Hocko wrote: >> On Fri 25-08-17 09:28:19, Pavel Machek wrote: >> > On Fri 2017-08-25 08:35:46, Michal Hocko wrote: >> > > On Wed 23-08-17 19:57:09, Pavel Machek wrote: >> [...] >> > > > Dunno. < 1msec probably is

Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally

On Fri, Aug 25, 2017 at 04:18:18PM -0700, Stephen Boyd wrote: > On 08/25, Shawn Guo wrote: > > On Thu, Aug 24, 2017 at 11:37:01AM -0700, Stephen Boyd wrote: > > > On 08/24, Shawn Guo wrote: > > > > On Tue, Aug 22, 2017 at 01:31:32PM -0700, Stephen Boyd wrote: > > > > > Also, I see that on v4.13-rc

Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally

On Fri, Aug 25, 2017 at 04:18:18PM -0700, Stephen Boyd wrote: > On 08/25, Shawn Guo wrote: > > On Thu, Aug 24, 2017 at 11:37:01AM -0700, Stephen Boyd wrote: > > > On 08/24, Shawn Guo wrote: > > > > On Tue, Aug 22, 2017 at 01:31:32PM -0700, Stephen Boyd wrote: > > > > > Also, I see that on v4.13-rc

Re: [PATCH v4 0/2] Add support for MediaTek AHCI SATA

Hi Tejun, Just a gentle ping. I think others are okay with both :D Thanks. On Fri, 2017-08-18 at 09:13 +0800, Ryder Lee wrote: > Hi, > > This patch series add support for AHCI compatible SATA controller, and it is > compliant with the ahci 1.3 and sata 3.0 specification. This driver is >

Re: [PATCH v4 0/2] Add support for MediaTek AHCI SATA

Hi Tejun, Just a gentle ping. I think others are okay with both :D Thanks. On Fri, 2017-08-18 at 09:13 +0800, Ryder Lee wrote: > Hi, > > This patch series add support for AHCI compatible SATA controller, and it is > compliant with the ahci 1.3 and sata 3.0 specification. This driver is >

Re: pull-request: wireless-drivers 2017-08-25

From: Kalle Valo Date: Fri, 25 Aug 2017 16:37:57 +0300 > here's pull request to net tree for 4.13, more info in the signed > tag below. Please let me know if there are any problems. Pulled, thanks Kalle.

Re: pull-request: wireless-drivers 2017-08-25

From: Kalle Valo Date: Fri, 25 Aug 2017 16:37:57 +0300 > here's pull request to net tree for 4.13, more info in the signed > tag below. Please let me know if there are any problems. Pulled, thanks Kalle.

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

From: Romain Perier Date: Fri, 25 Aug 2017 08:49:59 +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 v5] net: stmmac: Delete dead code for MDIO registration

From: Romain Perier Date: Fri, 25 Aug 2017 08:49:59 +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] net: sxgbe: check memory allocation failure

From: Christophe JAILLET Date: Fri, 25 Aug 2017 07:35:51 +0200 > Check memory allocation failure and return -ENOMEM in such a case, as > already done few lines below for another memory allocation. > > Signed-off-by: Christophe JAILLET

Re: [PATCH] net: sxgbe: check memory allocation failure

From: Christophe JAILLET Date: Fri, 25 Aug 2017 07:35:51 +0200 > Check memory allocation failure and return -ENOMEM in such a case, as > already done few lines below for another memory allocation. > > Signed-off-by: Christophe JAILLET Applied, thank you.

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Fri, Aug 25, 2017 at 5:31 PM, Linus Torvalds wrote: > > It made it way more fragile and complicated, having to rewrite things > so carefully. A simple slab cache would likely be a lot cleaner and > simpler. It also turns out that despite all the interfaces, we

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Fri, Aug 25, 2017 at 5:31 PM, Linus Torvalds wrote: > > It made it way more fragile and complicated, having to rewrite things > so carefully. A simple slab cache would likely be a lot cleaner and > simpler. It also turns out that despite all the interfaces, we only really ever wait on two

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

On 2017/8/26 5:13, Thomas Gleixner wrote: > On Fri, 25 Aug 2017, zhong jiang wrote: >> From: zhong jiang >> Date: Fri, 25 Aug 2017 12:05:56 +0800 >> Subject: [PATCH v2] futex: avoid undefined behaviour when shift exponent is >> negative > Please do not send patches without

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

On 2017/8/26 5:13, Thomas Gleixner wrote: > On Fri, 25 Aug 2017, zhong jiang wrote: >> From: zhong jiang >> Date: Fri, 25 Aug 2017 12:05:56 +0800 >> Subject: [PATCH v2] futex: avoid undefined behaviour when shift exponent is >> negative > Please do not send patches without changing the subject

Re: [PATCH v11 2/6] ACPI: Add APEI GHES Table Generation support

Hi Shannon, On 2017/8/26 9:08, Shannon Zhao wrote: > > > On 2017/8/25 19:20, gengdongjiu wrote: diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c >> index 3d78ff6..def1ec1 100644 >> --- a/hw/arm/virt-acpi-build.c >> +++ b/hw/arm/virt-acpi-build.c >> @@ -45,6

Re: [PATCH v11 2/6] ACPI: Add APEI GHES Table Generation support

Hi Shannon, On 2017/8/26 9:08, Shannon Zhao wrote: > > > On 2017/8/25 19:20, gengdongjiu wrote: diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c >> index 3d78ff6..def1ec1 100644 >> --- a/hw/arm/virt-acpi-build.c >> +++ b/hw/arm/virt-acpi-build.c >> @@ -45,6

Re: [PATCH v3 0/5] Add MediaTek PMIC keys support

Sorry for missing the change history. Changes since v2: - use standard properties for keycodes and debounce time - change to use platform_get_irq in leaf drivers - use better ways to define IRQ resources Changes since v1: - create irq mappings in mfd core driver instead of leaf drivers - remove

Re: [PATCH v3 0/5] Add MediaTek PMIC keys support

Sorry for missing the change history. Changes since v2: - use standard properties for keycodes and debounce time - change to use platform_get_irq in leaf drivers - use better ways to define IRQ resources Changes since v1: - create irq mappings in mfd core driver instead of leaf drivers - remove

Re: [patch V2 35/44] x86/idt: Switch early trap init to IDT tables

On 08/25/2017 05:47 PM, Thomas Gleixner wrote: > > -/* Set of traps needed for early debugging. */ > -void __init early_trap_init(void) > -{ > - /* > - * Don't use IST to set DEBUG_STACK as it doesn't work until TSS > - * is ready in cpu_init() <-- trap_init(). Before trap_init(),

Re: [patch V2 35/44] x86/idt: Switch early trap init to IDT tables

On 08/25/2017 05:47 PM, Thomas Gleixner wrote: > > -/* Set of traps needed for early debugging. */ > -void __init early_trap_init(void) > -{ > - /* > - * Don't use IST to set DEBUG_STACK as it doesn't work until TSS > - * is ready in cpu_init() <-- trap_init(). Before trap_init(),

Re: [patch V2 25/44] x86: Replace access to desc_struct:a/b fields

On 08/25/2017 05:47 PM, Thomas Gleixner wrote: > The union inside of desc_struct which allows access to the raw u32 parts of > the descriptors. This raw access part is about to go away. > > Replace the few code parts which access those fields. > > Signed-off-by: Thomas Gleixner

Re: [patch V2 25/44] x86: Replace access to desc_struct:a/b fields

On 08/25/2017 05:47 PM, Thomas Gleixner wrote: > The union inside of desc_struct which allows access to the raw u32 parts of > the descriptors. This raw access part is about to go away. > > Replace the few code parts which access those fields. > > Signed-off-by: Thomas Gleixner > Cc: Boris

Re: [PATCH v11 1/6] ACPI: add APEI/HEST/CPER structures and macros

On 2017/8/26 9:00, Shannon Zhao wrote: > > > On 2017/8/25 18:37, gengdongjiu wrote: + >> +/* From the ACPI 6.1 spec, "18.3.2.9 Hardware Error Notification" */ >> + It's better to refer to the first spec version of this structure and same with others you define. >> do

Re: [PATCH v11 1/6] ACPI: add APEI/HEST/CPER structures and macros

On 2017/8/26 9:00, Shannon Zhao wrote: > > > On 2017/8/25 18:37, gengdongjiu wrote: + >> +/* From the ACPI 6.1 spec, "18.3.2.9 Hardware Error Notification" */ >> + It's better to refer to the first spec version of this structure and same with others you define. >> do

[PATCH net-next v3] e1000e: Be drop monitor friendly

e1000e_put_txbuf() can be called from normal reclamation path as well as when a DMA mapping failure, so we need to differentiate these two cases when freeing SKBs to be drop monitor friendly. e1000e_tx_hwtstamp_work() and e1000_remove() are processing TX timestamped SKBs and those should not be

[PATCH net-next v3] e1000e: Be drop monitor friendly

e1000e_put_txbuf() can be called from normal reclamation path as well as when a DMA mapping failure, so we need to differentiate these two cases when freeing SKBs to be drop monitor friendly. e1000e_tx_hwtstamp_work() and e1000_remove() are processing TX timestamped SKBs and those should not be

Re: linux-next: build warnings after merge of the akpm-current tree

Hi Andrew, On 2017/8/26 5:24, Andrew Morton wrote: > On Thu, 24 Aug 2017 08:15:30 + Changwei Ge wrote: > >> Hi Andrew, >> >> On 2017/8/24 15:42, Stephen Rothwell wrote: >>> Hi Andrew, After merging the akpm-current tree, today's linux-next >>> build (x86_64

Re: linux-next: build warnings after merge of the akpm-current tree

Hi Andrew, On 2017/8/26 5:24, Andrew Morton wrote: > On Thu, 24 Aug 2017 08:15:30 + Changwei Ge wrote: > >> Hi Andrew, >> >> On 2017/8/24 15:42, Stephen Rothwell wrote: >>> Hi Andrew, After merging the akpm-current tree, today's linux-next >>> build (x86_64 allmodconfig) produced these

Re: [PATCH net-next v7 05/10] landlock: Add LSM hooks related to filesystem

On Fri, Aug 25, 2017 at 10:16:39AM +0200, Mickaël Salaün wrote: > > > >> +/* WRAP_ARG_SB */ > >> +#define WRAP_ARG_SB_TYPE WRAP_TYPE_FS > >> +#define WRAP_ARG_SB_DEC(arg) \ > >> + EXPAND_C(WRAP_TYPE_FS) wrap_##arg = \ > >> + { .type =

Re: [PATCH net-next v7 05/10] landlock: Add LSM hooks related to filesystem

On Fri, Aug 25, 2017 at 10:16:39AM +0200, Mickaël Salaün wrote: > > > >> +/* WRAP_ARG_SB */ > >> +#define WRAP_ARG_SB_TYPE WRAP_TYPE_FS > >> +#define WRAP_ARG_SB_DEC(arg) \ > >> + EXPAND_C(WRAP_TYPE_FS) wrap_##arg = \ > >> + { .type =

Re: [PATCH 3.16 124/134] net/mlx4_en: Avoid adding steering rules with invalid ring

On Sun, 2017-08-20 at 12:19 +0300, Tariq Toukan wrote: > On 18/08/2017 4:13 PM, Ben Hutchings wrote: > > 3.16.47-rc1 review patch.  If anyone has any objections, please let me know. > > Please notice that there's a fix for this patch, here: > > 6dc06c08bef1 net/mlx4: Fix the check in attaching

Re: [PATCH 3.16 124/134] net/mlx4_en: Avoid adding steering rules with invalid ring

On Sun, 2017-08-20 at 12:19 +0300, Tariq Toukan wrote: > On 18/08/2017 4:13 PM, Ben Hutchings wrote: > > 3.16.47-rc1 review patch.  If anyone has any objections, please let me know. > > Please notice that there's a fix for this patch, here: > > 6dc06c08bef1 net/mlx4: Fix the check in attaching

Re: [PATCH v11 2/6] ACPI: Add APEI GHES Table Generation support

On 2017/8/25 19:20, gengdongjiu wrote: >>> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c >>> >> index 3d78ff6..def1ec1 100644 >>> >> --- a/hw/arm/virt-acpi-build.c >>> >> +++ b/hw/arm/virt-acpi-build.c >>> >> @@ -45,6 +45,7 @@ >>> >> #include "hw/arm/virt.h" >>> >> #include

Re: [PATCH v11 2/6] ACPI: Add APEI GHES Table Generation support

On 2017/8/25 19:20, gengdongjiu wrote: >>> diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c >>> >> index 3d78ff6..def1ec1 100644 >>> >> --- a/hw/arm/virt-acpi-build.c >>> >> +++ b/hw/arm/virt-acpi-build.c >>> >> @@ -45,6 +45,7 @@ >>> >> #include "hw/arm/virt.h" >>> >> #include

Re: [PATCH net-next v7 01/10] selftest: Enhance kselftest_harness.h with a step mechanism

On Fri, Aug 25, 2017 at 09:58:33AM +0200, Mickaël Salaün wrote: > > > On 24/08/2017 04:31, Alexei Starovoitov wrote: > > On Mon, Aug 21, 2017 at 02:09:24AM +0200, Mickaël Salaün wrote: > >> This step mechanism may be useful to return an information about the > >> error without being able to

Re: [PATCH net-next v7 01/10] selftest: Enhance kselftest_harness.h with a step mechanism

On Fri, Aug 25, 2017 at 09:58:33AM +0200, Mickaël Salaün wrote: > > > On 24/08/2017 04:31, Alexei Starovoitov wrote: > > On Mon, Aug 21, 2017 at 02:09:24AM +0200, Mickaël Salaün wrote: > >> This step mechanism may be useful to return an information about the > >> error without being able to

Re: [PATCH] staging:rtl8712:xmit_linux.c: Avoid CamelCase

On Sat, 2017-08-26 at 01:21 +0530, Harsha Sharma wrote: > Hello, > > Sorry, this was my first contribution in linux-kernel. I will take care > about this from next time. > Do I need to send these patches once again one by one? No, just pick the "best" one of what you sent without any of the

Re: [PATCH] staging:rtl8712:xmit_linux.c: Avoid CamelCase

On Sat, 2017-08-26 at 01:21 +0530, Harsha Sharma wrote: > Hello, > > Sorry, this was my first contribution in linux-kernel. I will take care > about this from next time. > Do I need to send these patches once again one by one? No, just pick the "best" one of what you sent without any of the

Re: [PATCH v11 1/6] ACPI: add APEI/HEST/CPER structures and macros

On 2017/8/25 18:37, gengdongjiu wrote: >>> + >>> >> +/* From the ACPI 6.1 spec, "18.3.2.9 Hardware Error Notification" */ >>> >> + >> > It's better to refer to the first spec version of this structure and >> > same with others you define. > do you mean which spec version? the definition is

Re: [PATCH v11 1/6] ACPI: add APEI/HEST/CPER structures and macros

On 2017/8/25 18:37, gengdongjiu wrote: >>> + >>> >> +/* From the ACPI 6.1 spec, "18.3.2.9 Hardware Error Notification" */ >>> >> + >> > It's better to refer to the first spec version of this structure and >> > same with others you define. > do you mean which spec version? the definition is

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

On Thu, Aug 24, 2017 at 4:37 PM, Christian Brauner wrote: > > In fact, /dev/ptmx being a symlink or bind-mount is the *standard* in > containers > even for non-user namespaced containers or containers that do not retain > CAP_MKNOD. Yes. I think using

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

On Thu, Aug 24, 2017 at 4:37 PM, Christian Brauner wrote: > > In fact, /dev/ptmx being a symlink or bind-mount is the *standard* in > containers > even for non-user namespaced containers or containers that do not retain > CAP_MKNOD. Yes. I think using /dev/pts/ptmx is nice from a kernel

[PATCH 1/9] ASoC: max98927: Added TDM support

Signed-off-by: Ryan Lee --- Changes : Added code to support TDM mode sound/soc/codecs/max98927.c | 141 sound/soc/codecs/max98927.h | 6 +- 2 files changed, 120 insertions(+), 27 deletions(-) diff --git

[PATCH 1/9] ASoC: max98927: Added TDM support

Signed-off-by: Ryan Lee --- Changes : Added code to support TDM mode sound/soc/codecs/max98927.c | 141 sound/soc/codecs/max98927.h | 6 +- 2 files changed, 120 insertions(+), 27 deletions(-) diff --git a/sound/soc/codecs/max98927.c

[PATCH 5/9] ASoC: max98927: Removed obsolete variables

Signed-off-by: Ryan Lee --- Changes : Removed obsolete variables from max98927_priv sound/soc/codecs/max98927.h | 4 1 file changed, 4 deletions(-) mode change 100644 => 100755 sound/soc/codecs/max98927.h diff --git a/sound/soc/codecs/max98927.h

[PATCH 5/9] ASoC: max98927: Removed obsolete variables

Signed-off-by: Ryan Lee --- Changes : Removed obsolete variables from max98927_priv sound/soc/codecs/max98927.h | 4 1 file changed, 4 deletions(-) mode change 100644 => 100755 sound/soc/codecs/max98927.h diff --git a/sound/soc/codecs/max98927.h b/sound/soc/codecs/max98927.h old mode

[PATCH 6/9] ASoC: max98927: Modified chip default register values

Signed-off-by: Ryan Lee --- Changes : Updated chip default register values sound/soc/codecs/max98927.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index 208d5ba..3ab8220

[PATCH 6/9] ASoC: max98927: Modified chip default register values

Signed-off-by: Ryan Lee --- Changes : Updated chip default register values sound/soc/codecs/max98927.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index 208d5ba..3ab8220 100644 ---

[PATCH 3/9] ASoC: max98927: Updated volatile register list

Signed-off-by: Ryan Lee --- Changes : Added more reigsters into volatile register list sound/soc/codecs/max98927.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index 1dfcb7b..c72a244 100644

[PATCH 3/9] ASoC: max98927: Updated volatile register list

Signed-off-by: Ryan Lee --- Changes : Added more reigsters into volatile register list sound/soc/codecs/max98927.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index 1dfcb7b..c72a244 100644 --- a/sound/soc/codecs/max98927.c

[PATCH 9/9] ASoC: max98927: Changed device property read function

Signed-off-by: Ryan Lee --- Changes : Replaced 'of_property_read_u32' by 'device_property_read_u32' sound/soc/codecs/max98927.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c

[PATCH 7/9] ASoC: max98927: Added PM suspend and resume function

Signed-off-by: Ryan Lee --- Changes : added PM suspend and resume function to keep register values from power down sound/soc/codecs/max98927.c | 27 ++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git

[PATCH 9/9] ASoC: max98927: Changed device property read function

Signed-off-by: Ryan Lee --- Changes : Replaced 'of_property_read_u32' by 'device_property_read_u32' sound/soc/codecs/max98927.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index f944659..4867f78 100644 ---

[PATCH 7/9] ASoC: max98927: Added PM suspend and resume function

Signed-off-by: Ryan Lee --- Changes : added PM suspend and resume function to keep register values from power down sound/soc/codecs/max98927.c | 27 ++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/sound/soc/codecs/max98927.c

[PATCH 8/9] ASoC: max98927: Modified DAPM widget and map to enable/disable VI sense path

Signed-off-by: Ryan Lee --- Changes : Modified DAPM widget and audio map to enable/disable IV sensing path sound/soc/codecs/max98927.c | 28 +--- 1 file changed, 17 insertions(+), 11 deletions(-) diff --git a/sound/soc/codecs/max98927.c

[PATCH 2/9] ASoC: max98927: Added controls for Envelope tracking

Signed-off-by: Ryan Lee --- Changes : Added controls to support envelope tracking function sound/soc/codecs/max98927.c | 20 sound/soc/codecs/max98927.h | 4 2 files changed, 20 insertions(+), 4 deletions(-) diff --git

[PATCH 4/9] ASoC: max98927: Added missing \n to end of dev_err messages

Signed-off-by: Ryan Lee --- Changes : added missing \n to end of dev_err sound/soc/codecs/max98927.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index c72a244..208d5ba 100644

[PATCH 8/9] ASoC: max98927: Modified DAPM widget and map to enable/disable VI sense path

Signed-off-by: Ryan Lee --- Changes : Modified DAPM widget and audio map to enable/disable IV sensing path sound/soc/codecs/max98927.c | 28 +--- 1 file changed, 17 insertions(+), 11 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c

[PATCH 2/9] ASoC: max98927: Added controls for Envelope tracking

Signed-off-by: Ryan Lee --- Changes : Added controls to support envelope tracking function sound/soc/codecs/max98927.c | 20 sound/soc/codecs/max98927.h | 4 2 files changed, 20 insertions(+), 4 deletions(-) diff --git a/sound/soc/codecs/max98927.c

[PATCH 4/9] ASoC: max98927: Added missing \n to end of dev_err messages

Signed-off-by: Ryan Lee --- Changes : added missing \n to end of dev_err sound/soc/codecs/max98927.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sound/soc/codecs/max98927.c b/sound/soc/codecs/max98927.c index c72a244..208d5ba 100644 ---

Re: [PATCH 3.16 084/134] usb: misc: legousbtower: Fix buffers on stack

On Sat, 2017-08-19 at 09:29 +0300, Maksim Salau wrote: > On Fri, 18 Aug 2017 14:13:20 +0100 > Ben Hutchings wrote: > > > 3.16.47-rc1 review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Maksim Salau

Re: [PATCH 3.16 084/134] usb: misc: legousbtower: Fix buffers on stack

On Sat, 2017-08-19 at 09:29 +0300, Maksim Salau wrote: > On Fri, 18 Aug 2017 14:13:20 +0100 > Ben Hutchings wrote: > > > 3.16.47-rc1 review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Maksim Salau > > > > commit

Re: [PATCH 3.16 032/134] MIPS: Loongson-3: Select MIPS_L1_CACHE_SHIFT_6

On Mon, 2017-08-21 at 10:24 +0800, Huacai Chen wrote: > 3.16 doesn't need this, because 3.16 doesn't support Loongson-3 R2/R3. Thanks, I'll drop this. Ben. > Huacai > > > On Fri, Aug 18, 2017 at 9:13 PM, Ben Hutchings wrote: > > 3.16.47-rc1 review patch.  If anyone has

Re: [PATCH 3.16 032/134] MIPS: Loongson-3: Select MIPS_L1_CACHE_SHIFT_6

On Mon, 2017-08-21 at 10:24 +0800, Huacai Chen wrote: > 3.16 doesn't need this, because 3.16 doesn't support Loongson-3 R2/R3. Thanks, I'll drop this. Ben. > Huacai > > > On Fri, Aug 18, 2017 at 9:13 PM, Ben Hutchings wrote: > > 3.16.47-rc1 review patch.  If anyone has any objections, please

Re: [PATCH 3.16 119/134] ipv4: restore rt->fi for reference counting

On Fri, 2017-08-18 at 06:53 -0700, Eric Dumazet wrote: > > On Fri, Aug 18, 2017 at 6:13 AM, Ben Hutchings wrote: > > 3.16.47-rc1 review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: WANG Cong >

Re: [PATCH 3.16 119/134] ipv4: restore rt->fi for reference counting

On Fri, 2017-08-18 at 06:53 -0700, Eric Dumazet wrote: > > On Fri, Aug 18, 2017 at 6:13 AM, Ben Hutchings wrote: > > 3.16.47-rc1 review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: WANG Cong > > > > commit

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Fri, Aug 25, 2017 at 4:03 PM, Linus Torvalds wrote: > > Let this be a lesson in just *how* little tested, and *how* crap that > patch probably still is. I haven't had time to look at it any more (trying to merge the pull requests that came in today instead), but

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Fri, Aug 25, 2017 at 4:03 PM, Linus Torvalds wrote: > > Let this be a lesson in just *how* little tested, and *how* crap that > patch probably still is. I haven't had time to look at it any more (trying to merge the pull requests that came in today instead), but the more I think about it, the

Re: [RFC PATCH] mm: fadvise: avoid fadvise for fs without backing device

On Fri, Aug 25, 2017 at 2:49 PM, Andrew Morton wrote: > On Thu, 17 Aug 2017 18:20:17 -0700 Shakeel Butt wrote: > >> +linux-mm, linux-kernel >> >> On Thu, Aug 17, 2017 at 6:10 PM, Shakeel Butt wrote: >> > The fadvise() manpage

Re: [RFC PATCH] mm: fadvise: avoid fadvise for fs without backing device

On Fri, Aug 25, 2017 at 2:49 PM, Andrew Morton wrote: > On Thu, 17 Aug 2017 18:20:17 -0700 Shakeel Butt wrote: > >> +linux-mm, linux-kernel >> >> On Thu, Aug 17, 2017 at 6:10 PM, Shakeel Butt wrote: >> > The fadvise() manpage is silent on fadvise()'s effect on >> > memory-based filesystems

[PATCH] mm/hmm: fix build when HMM is disabled

From: Jérôme Glisse Combinatorial Kconfig is painfull. Withi this patch all below combination build. 1) 2) CONFIG_HMM_MIRROR=y 3) CONFIG_DEVICE_PRIVATE=y 4) CONFIG_DEVICE_PUBLIC=y 5) CONFIG_HMM_MIRROR=y CONFIG_DEVICE_PUBLIC=y 6) CONFIG_HMM_MIRROR=y

[PATCH] mm/hmm: fix build when HMM is disabled

From: Jérôme Glisse Combinatorial Kconfig is painfull. Withi this patch all below combination build. 1) 2) CONFIG_HMM_MIRROR=y 3) CONFIG_DEVICE_PRIVATE=y 4) CONFIG_DEVICE_PUBLIC=y 5) CONFIG_HMM_MIRROR=y CONFIG_DEVICE_PUBLIC=y 6) CONFIG_HMM_MIRROR=y CONFIG_DEVICE_PRIVATE=y 7)

kernel panic in generic_make_request() in block/blk-core.c

Hi All, I am trying to use the latest (4.13-rc6) kernel in my android device (Intel APL SOC, running Android O). But sometimes, during the boot process, when MMC partition is getting mounted, I hit the following kernel panic. Its not 100% reproducible. But I hit it twice in 10 cycles. Copied

kernel panic in generic_make_request() in block/blk-core.c

Hi All, I am trying to use the latest (4.13-rc6) kernel in my android device (Intel APL SOC, running Android O). But sometimes, during the boot process, when MMC partition is getting mounted, I hit the following kernel panic. Its not 100% reproducible. But I hit it twice in 10 cycles. Copied

Re: mmotm 2017-08-25-15-50 uploaded

On 08/25/17 15:50, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2017-08-25-15-50 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my

Re: mmotm 2017-08-25-15-50 uploaded

On 08/25/17 15:50, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2017-08-25-15-50 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my

Re: + mm-madvise-fix-freeing-of-locked-page-with-madv_free.patch added to -mm tree

On 08/25/2017 03:51 PM, Nadav Amit wrote: > Mike Kravetz wrote: > >> On 08/25/2017 03:02 PM, Nadav Amit wrote: >>> Michal Hocko wrote: >>> Hmm, I do not see this neither in linux-mm nor LKML. Strange On Wed 23-08-17 14:41:21, Andrew

Re: + mm-madvise-fix-freeing-of-locked-page-with-madv_free.patch added to -mm tree

On 08/25/2017 03:51 PM, Nadav Amit wrote: > Mike Kravetz wrote: > >> On 08/25/2017 03:02 PM, Nadav Amit wrote: >>> Michal Hocko wrote: >>> Hmm, I do not see this neither in linux-mm nor LKML. Strange On Wed 23-08-17 14:41:21, Andrew Morton wrote: > From: Eric Biggers >

[PATCH] tpm/tpm_crb: Use start method value from ACPI table directly

This patch gets rid of dealing with intermediate flag for start method and use start method value from ACPI table directly. For ARM64, the locality is handled by Trust Zone in FW. The layout does not have crb_regs_head. It is hitting the following line. dev_warn(dev, FW_BUG "Bad ACPI memory

[PATCH] tpm/tpm_crb: Use start method value from ACPI table directly

This patch gets rid of dealing with intermediate flag for start method and use start method value from ACPI table directly. For ARM64, the locality is handled by Trust Zone in FW. The layout does not have crb_regs_head. It is hitting the following line. dev_warn(dev, FW_BUG "Bad ACPI memory

Re: [PATCH V1] thermal: qcom-spmi-temp-alarm: add support for GEN2 PMIC peripherals

On 08/25, Zhang Rui wrote: > On Thu, 2017-08-17 at 13:12 +0530, kgu...@codeaurora.org wrote: > > On 2017-08-16 17:53, kgu...@codeaurora.org wrote: > > > > > > On 2017-08-08 13:42, Zhang Rui wrote: > > > > > > > > On Thu, 2017-07-13 at 17:39 +0530, Kiran Gunda wrote: > > > > > > > > > > From:

Re: [PATCH V1] thermal: qcom-spmi-temp-alarm: add support for GEN2 PMIC peripherals

On 08/25, Zhang Rui wrote: > On Thu, 2017-08-17 at 13:12 +0530, kgu...@codeaurora.org wrote: > > On 2017-08-16 17:53, kgu...@codeaurora.org wrote: > > > > > > On 2017-08-08 13:42, Zhang Rui wrote: > > > > > > > > On Thu, 2017-07-13 at 17:39 +0530, Kiran Gunda wrote: > > > > > > > > > > From:

Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally

On 08/25, Shawn Guo wrote: > On Thu, Aug 24, 2017 at 11:37:01AM -0700, Stephen Boyd wrote: > > On 08/24, Shawn Guo wrote: > > > On Tue, Aug 22, 2017 at 01:31:32PM -0700, Stephen Boyd wrote: > > > > Also, I see that on v4.13-rc series the read/write checks are > > > > causing the led driver to fail

Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally

On 08/25, Shawn Guo wrote: > On Thu, Aug 24, 2017 at 11:37:01AM -0700, Stephen Boyd wrote: > > On 08/24, Shawn Guo wrote: > > > On Tue, Aug 22, 2017 at 01:31:32PM -0700, Stephen Boyd wrote: > > > > Also, I see that on v4.13-rc series the read/write checks are > > > > causing the led driver to fail

Re: [PATCH 1/3] usb: dwc2: Improve gadget state disconnection handling

On Thu, Aug 17, 2017 at 12:03 PM, John Stultz wrote: > In the earlier commit dad3f793f20f ("usb: dwc2: Make sure we > disconnect the gadget state"), I was trying to fix up the > fact that we somehow weren't disconnecting the gadget state, > so that when the OTG port was

Re: [PATCH 1/3] usb: dwc2: Improve gadget state disconnection handling

On Thu, Aug 17, 2017 at 12:03 PM, John Stultz wrote: > In the earlier commit dad3f793f20f ("usb: dwc2: Make sure we > disconnect the gadget state"), I was trying to fix up the > fact that we somehow weren't disconnecting the gadget state, > so that when the OTG port was plugged in the second time

Re: [PATCH] usb: dwc3: Initialize DMA ops/mask for xhci-hcd

On 08/25/2017 01:02 PM, Adam Wallis wrote: The dma ops from the parent DWC device are not getting passed to the child xhci-hcd device. This patch makes use of platform_device_register_full to set the DMA ops. For the DT/OF case, dma_ops were still null after the the device register, so

Re: [PATCH] usb: dwc3: Initialize DMA ops/mask for xhci-hcd

On 08/25/2017 01:02 PM, Adam Wallis wrote: The dma ops from the parent DWC device are not getting passed to the child xhci-hcd device. This patch makes use of platform_device_register_full to set the DMA ops. For the DT/OF case, dma_ops were still null after the the device register, so

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Fri, Aug 25, 2017 at 3:51 PM, Linus Torvalds wrote: > > So take it as that: example pseudo-code that happens to pass a > compiler, but is meant as a RFD rather than actually working. Oh, and after I sent it out, I wanted to look once again, and realized that the

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Fri, Aug 25, 2017 at 3:51 PM, Linus Torvalds wrote: > > So take it as that: example pseudo-code that happens to pass a > compiler, but is meant as a RFD rather than actually working. Oh, and after I sent it out, I wanted to look once again, and realized that the "remove_myself_from()"

[RFC][PATCH] time: Fix ktime_get_raw() issues caused by incorrect base accumulation

In commit fc6eead7c1e2 ("time: Clean up CLOCK_MONOTONIC_RAW time handling"), I mistakenly added the following: /* Update the monotonic raw base */ seconds = tk->raw_sec; nsec = (u32)(tk->tkr_raw.xtime_nsec >> tk->tkr_raw.shift); tk->tkr_raw.base = ns_to_ktime(seconds * NSEC_PER_SEC + nsec);

[RFC][PATCH] time: Fix ktime_get_raw() issues caused by incorrect base accumulation

In commit fc6eead7c1e2 ("time: Clean up CLOCK_MONOTONIC_RAW time handling"), I mistakenly added the following: /* Update the monotonic raw base */ seconds = tk->raw_sec; nsec = (u32)(tk->tkr_raw.xtime_nsec >> tk->tkr_raw.shift); tk->tkr_raw.base = ns_to_ktime(seconds * NSEC_PER_SEC + nsec);

[GIT PULL] MTD fixes for v4.13-rc7

9a51544774a57fcb94994a61860a17f9e63a8d7b: mtd: blkdevs: Fix mtd block write failure (2017-08-12 14:53:24 -0700) are available in the git repository at: git://git.infradead.org/linux-mtd.git tags/for-linus-20170825 for you to fetch changes up to be3e83e3471cd0faff2c2d88fe9cfc73d9a9745a: mtd: nand

Re: [PATCH v5 1/2] sched/clock: interface to allow timestamps early in boot

On Wed, 23 Aug 2017, Pavel Tatashin wrote: > > - Use weak sched_clock_early() interface to determine time from boot in > arch specific read_boot_clock64() weak sched_clock_early() is not an interface. The weak implementation is merily a place holder which can be overridden by a real

  1   2   3   4   5   6   7   8   9   10   >