[PATCH v7] usb: serial: add vid:pid for Cypress WICED dev board

This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message. >From 891fe3887b53d2bad35d3f94c845ecb89ab58509 Mon Sep 17 00:00:00 2001 From: Jeffrey Chu

[PATCH v7] usb: serial: add vid:pid for Cypress WICED dev board

This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message. >From 891fe3887b53d2bad35d3f94c845ecb89ab58509 Mon Sep 17 00:00:00 2001 From: Jeffrey Chu

[PULL] Please pull JSON Metrics for Intel CPUs

Hi Arnaldo, Now that the metrics patchkit has been merged, the actual JSON metrics for Intel CPUs can be merged. Please pull this version. It includes Skylake Server support and was rebased. Thanks, -Andi The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9: Merge tag

[PULL] Please pull JSON Metrics for Intel CPUs

Hi Arnaldo, Now that the metrics patchkit has been merged, the actual JSON metrics for Intel CPUs can be merged. Please pull this version. It includes Skylake Server support and was rebased. Thanks, -Andi The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9: Merge tag

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

On Fri, Sep 8, 2017 at 10:22 AM, Linus Torvalds wrote: > > Of course, I only did a "make allmodconfig" to test the MODVERSIONS > case, I didn't actually install the modules. Is that error perhaps > only detected at install time? Oh, I take that back. I just got a

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

On Fri, Sep 8, 2017 at 10:22 AM, Linus Torvalds wrote: > > Of course, I only did a "make allmodconfig" to test the MODVERSIONS > case, I didn't actually install the modules. Is that error perhaps > only detected at install time? Oh, I take that back. I just got a ton of warnings with my

Re: [PATCH v5 3/3] perf config: Allow creating empty config set for config file autogeneration

Thank you !! :) - Taeung On 09/08/2017 11:36 PM, Arnaldo Carvalho de Melo wrote: Em Thu, Sep 07, 2017 at 12:18:56PM +0900, Taeung Song escreveu: When there isn't a config file (e.g. ~/.perfconfig) or it has nothing, the config set wasn't created. If the config set not exists, a config file

Re: [PATCH v5 3/3] perf config: Allow creating empty config set for config file autogeneration

Thank you !! :) - Taeung On 09/08/2017 11:36 PM, Arnaldo Carvalho de Melo wrote: Em Thu, Sep 07, 2017 at 12:18:56PM +0900, Taeung Song escreveu: When there isn't a config file (e.g. ~/.perfconfig) or it has nothing, the config set wasn't created. If the config set not exists, a config file

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

On Thu, Sep 07, 2017 at 11:26:47PM +0200, Ingo Molnar wrote: > > * Eric Biggers wrote: > > > On Thu, Sep 07, 2017 at 09:15:34AM +0200, Ingo Molnar wrote: > > > > > > * Eric Biggers wrote: > > > > > > > Thanks for fixing these! I don't have time to

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

On Thu, Sep 07, 2017 at 11:26:47PM +0200, Ingo Molnar wrote: > > * Eric Biggers wrote: > > > On Thu, Sep 07, 2017 at 09:15:34AM +0200, Ingo Molnar wrote: > > > > > > * Eric Biggers wrote: > > > > > > > Thanks for fixing these! I don't have time to review these in detail, > > > > but I ran

[PATCH v3 0/2] ARM: dts: keystone-k2g: Add I2C support for 66AK2G

Add I2C support to 66AK2G. Primary requirement is to add PM Runtime support to the driver. This has been tested on following platforms by performing simple i2c test such as i2c detect and reading on board i2c devices: K2G GP evm OMAPL138 K2L GP EVM and boot tested on: K2E GP EVM K2HK GP EVM

[PATCH v3 0/2] ARM: dts: keystone-k2g: Add I2C support for 66AK2G

Add I2C support to 66AK2G. Primary requirement is to add PM Runtime support to the driver. This has been tested on following platforms by performing simple i2c test such as i2c detect and reading on board i2c devices: K2G GP evm OMAPL138 K2L GP EVM and boot tested on: K2E GP EVM K2HK GP EVM

[PATCH v3 1/2] i2c: davinci: Add PM Runtime Support

66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime is required to insure the power domain used by the specific I2C instance is properly turned on along with its functional clock. Signed-off-by: Franklin S Cooper

[PATCH v3 1/2] i2c: davinci: Add PM Runtime Support

66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime is required to insure the power domain used by the specific I2C instance is properly turned on along with its functional clock. Signed-off-by: Franklin S Cooper

Re: [PATCH] ALSA: msnd: Optimize / harden DSP and MIDI loops

>> Hi Greg, >> >> Could you please apply it for 4.4-stable. >> This fixes https://nvd.nist.gov/vuln/detail/CVE-2017-9985 > > This vulnerability is just non-issue. You can't get it working > practically; it requires a modified hardware of the decade old ISA > sound card, and yet the system has to

Re: [PATCH] ALSA: msnd: Optimize / harden DSP and MIDI loops

>> Hi Greg, >> >> Could you please apply it for 4.4-stable. >> This fixes https://nvd.nist.gov/vuln/detail/CVE-2017-9985 > > This vulnerability is just non-issue. You can't get it working > practically; it requires a modified hardware of the decade old ISA > sound card, and yet the system has to

[PATCH] HID: i2c-hid: allocate hid buffers for real worst case

From: Adrian Salido The buffer allocation is not currently accounting for an extra byte for the report id. This can cause an out of bounds access in function i2c_hid_set_or_send_report() with reportID > 15. Signed-off-by: Guenter Roeck Signed-off-by:

[PATCH v3 2/2] dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm property

Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G unique clocks property usage. Signed-off-by: Franklin S Cooper Jr Acked-by: Rob Herring Acked-by: Sekhar Nori --- Documentation/devicetree/bindings/i2c/i2c-davinci.txt

[PATCH] HID: i2c-hid: allocate hid buffers for real worst case

From: Adrian Salido The buffer allocation is not currently accounting for an extra byte for the report id. This can cause an out of bounds access in function i2c_hid_set_or_send_report() with reportID > 15. Signed-off-by: Guenter Roeck Signed-off-by: Dmitry Torokhov ---

[PATCH v3 2/2] dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm property

Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G unique clocks property usage. Signed-off-by: Franklin S Cooper Jr Acked-by: Rob Herring Acked-by: Sekhar Nori --- Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12 1 file changed, 12

Re: [PATCH 3/3] block/loop: make loop cgroup aware

Hello, Shaohua. On Fri, Sep 08, 2017 at 10:07:15AM -0700, Shaohua Li wrote: > > The fact that we're forwarding explicitly in loop still bothers me a > > bit. Can you please elaborate why we don't want to do this > > generically through aio? > > I think we must forward in loop, because each cmd

RE: [PATCH RFC 3/5] Add KSZ8795 switch driver

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Friday, September 08, 2017 2:19 AM > To: Tristram Ha - C24268 > Cc: and...@lunn.ch; muva...@gmail.com; nathan.leigh.con...@gmail.com; > vivien.dide...@savoirfairelinux.com; f.faine...@gmail.com; >

Re: [PATCH 3/3] block/loop: make loop cgroup aware

Hello, Shaohua. On Fri, Sep 08, 2017 at 10:07:15AM -0700, Shaohua Li wrote: > > The fact that we're forwarding explicitly in loop still bothers me a > > bit. Can you please elaborate why we don't want to do this > > generically through aio? > > I think we must forward in loop, because each cmd

RE: [PATCH RFC 3/5] Add KSZ8795 switch driver

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Friday, September 08, 2017 2:19 AM > To: Tristram Ha - C24268 > Cc: and...@lunn.ch; muva...@gmail.com; nathan.leigh.con...@gmail.com; > vivien.dide...@savoirfairelinux.com; f.faine...@gmail.com; >

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

I checked. __pmd() works. BTW, my sparc32 fix was added in linux-next on August 11th and __pmd() is there, too. This means __pmd() + my fix has survived for almost a month in linux-next. It should be good. -- Best Regards Yan Zi On 7 Sep 2017, at 23:43, Stephen Rothwell wrote: > Hi all, > > On

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

I checked. __pmd() works. BTW, my sparc32 fix was added in linux-next on August 11th and __pmd() is there, too. This means __pmd() + my fix has survived for almost a month in linux-next. It should be good. -- Best Regards Yan Zi On 7 Sep 2017, at 23:43, Stephen Rothwell wrote: > Hi all, > > On

[PATCH v3] staging: typec: tcpm: Rewrite comparison to NULL pointer

Make code more concise and readable Signed-off-by: Harsha Sharma --- Change in v3: -Change in subject and log message Change in v2: -Change in subject -Change in log message drivers/staging/typec/tcpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH v3] staging: typec: tcpm: Rewrite comparison to NULL pointer

Make code more concise and readable Signed-off-by: Harsha Sharma --- Change in v3: -Change in subject and log message Change in v2: -Change in subject -Change in log message drivers/staging/typec/tcpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[GIT PULL] ARC changes for 4.4-rc1

Hi Linus, We have a bigger set of updates for ARC this time (mostly because some couldn't make last release bus). Please pull. Thx, -Vineet ---> The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98: Linux 4.13-rc7 (2017-08-27 17:20:40 -0700) are available in

[GIT PULL] ARC changes for 4.4-rc1

Hi Linus, We have a bigger set of updates for ARC this time (mostly because some couldn't make last release bus). Please pull. Thx, -Vineet ---> The following changes since commit cc4a41fe5541a73019a864883297bd5043aa6d98: Linux 4.13-rc7 (2017-08-27 17:20:40 -0700) are available in

Re: [netfilter-core] [PATCH] netfilter: nat: constify rhashtable_params

On Fri, Sep 08, 2017 at 01:46:30PM +0200, Pablo Neira Ayuso wrote: > On Wed, Aug 30, 2017 at 05:18:04PM +0530, Arvind Yadav wrote: > > rhashtable_params are not supposed to change at runtime. All > > Functions rhashtable_* working with const rhashtable_params > > provided by . So mark the

Re: [netfilter-core] [PATCH] netfilter: nat: constify rhashtable_params

On Fri, Sep 08, 2017 at 01:46:30PM +0200, Pablo Neira Ayuso wrote: > On Wed, Aug 30, 2017 at 05:18:04PM +0530, Arvind Yadav wrote: > > rhashtable_params are not supposed to change at runtime. All > > Functions rhashtable_* working with const rhashtable_params > > provided by . So mark the

Re: [PATCH] can: check for null sk before deferencing it via the call to sock_net

On 09/08/2017 05:02 PM, Colin King wrote: From: Colin Ian King The assignment of net via call sock_net will dereference sk. This is performed before a sanity null check on sk, so there could be a potential null dereference on the sock_net call if sk is null. Fix

Re: [PATCH] can: check for null sk before deferencing it via the call to sock_net

On 09/08/2017 05:02 PM, Colin King wrote: From: Colin Ian King The assignment of net via call sock_net will dereference sk. This is performed before a sanity null check on sk, so there could be a potential null dereference on the sock_net call if sk is null. Fix this by assigning net after

Re: kmemleak not always catching stuff

On Tue, Sep 05, 2017 at 10:15:45AM -0400, Steven Rostedt wrote: > On Mon, 4 Sep 2017 11:09:05 +0100 > Catalin Marinas wrote: > > On Fri, Sep 01, 2017 at 06:33:11PM -0400, Steven Rostedt wrote: > > > Now I was thinking that it may be due to the fact that the trampoline > >

Re: kmemleak not always catching stuff

On Tue, Sep 05, 2017 at 10:15:45AM -0400, Steven Rostedt wrote: > On Mon, 4 Sep 2017 11:09:05 +0100 > Catalin Marinas wrote: > > On Fri, Sep 01, 2017 at 06:33:11PM -0400, Steven Rostedt wrote: > > > Now I was thinking that it may be due to the fact that the trampoline > > > is allocated with

Re: [PATCH v3 00/20] Speculative page faults

On 08/09/2017 19:32, Laurent Dufour wrote: > This is a port on kernel 4.13 of the work done by Peter Zijlstra to > handle page fault without holding the mm semaphore [1]. Sorry for the noise, I got trouble sending the whole series through this email. I will try again. Cheers, Laurent.

Re: [PATCH 2/2] staging: typec: tcpm: Only request matching pdos

On Fri, Sep 8, 2017 at 2:36 AM, Dan Carpenter wrote: > On Thu, Sep 07, 2017 at 06:22:14PM -0700, Badhri Jagan Sridharan wrote: >> diff --git a/drivers/staging/typec/tcpm.c b/drivers/staging/typec/tcpm.c >> index 58a2c279f7d1..df0986d9f756 100644 >> ---

Re: [PATCH v3 00/20] Speculative page faults

On 08/09/2017 19:32, Laurent Dufour wrote: > This is a port on kernel 4.13 of the work done by Peter Zijlstra to > handle page fault without holding the mm semaphore [1]. Sorry for the noise, I got trouble sending the whole series through this email. I will try again. Cheers, Laurent.

Re: [PATCH 2/2] staging: typec: tcpm: Only request matching pdos

On Fri, Sep 8, 2017 at 2:36 AM, Dan Carpenter wrote: > On Thu, Sep 07, 2017 at 06:22:14PM -0700, Badhri Jagan Sridharan wrote: >> diff --git a/drivers/staging/typec/tcpm.c b/drivers/staging/typec/tcpm.c >> index 58a2c279f7d1..df0986d9f756 100644 >> --- a/drivers/staging/typec/tcpm.c >> +++

Re: [PATCH resend v2] power: supply: bq27xxx: enable writing capacity values for bq27421

> Am 08.09.2017 um 19:40 schrieb Pali Rohár : > > On Friday 08 September 2017 19:38:37 H. Nikolaus Schaller wrote: >> and here is the result: >> >>> root@letux:~# dmesg|fgrep bq27 >>> [ 10.391235] bq27xxx_battery_setup >>> [ 10.391265] bq27xxx_battery_setup:

Re: [PATCH resend v2] power: supply: bq27xxx: enable writing capacity values for bq27421

> Am 08.09.2017 um 19:40 schrieb Pali Rohár : > > On Friday 08 September 2017 19:38:37 H. Nikolaus Schaller wrote: >> and here is the result: >> >>> root@letux:~# dmesg|fgrep bq27 >>> [ 10.391235] bq27xxx_battery_setup >>> [ 10.391265] bq27xxx_battery_setup: dm_regs=bf0520e0 >>> [

[PATCH] HID: usbhid: get/put around clearing needs_remote_wakeup

From: Benson Leung usbhid->intf->needs_remote_wakeup is set when a device is opened, and is cleared when a device is closed. In usbhid_open, usb_autopm_get_interface is called before setting the needs_remote_wakeup flag, and usb_autopm_put_interface is called after

[PATCH] HID: usbhid: get/put around clearing needs_remote_wakeup

From: Benson Leung usbhid->intf->needs_remote_wakeup is set when a device is opened, and is cleared when a device is closed. In usbhid_open, usb_autopm_get_interface is called before setting the needs_remote_wakeup flag, and usb_autopm_put_interface is called after hid_start_in. However, when

Re: [Outreachy kernel] [PATCH v2] staging: typec: tcpm: Comparison to NULL pointer

Maybe "Rewrite comparison to NULL pointer" in the subject to include what was done, not just code was touched. On Fri, 8 Sep 2017, Harsha Sharma wrote: > Makes code more concise and readable Makes -> Make. Commit logs should be written in the imperative, like you are telling someone what to

Re: [Outreachy kernel] [PATCH v2] staging: typec: tcpm: Comparison to NULL pointer

Maybe "Rewrite comparison to NULL pointer" in the subject to include what was done, not just code was touched. On Fri, 8 Sep 2017, Harsha Sharma wrote: > Makes code more concise and readable Makes -> Make. Commit logs should be written in the imperative, like you are telling someone what to

[PATCH v2] staging: typec: tcpm: Comparison to NULL pointer

Makes code more concise and readable Signed-off-by: Harsha Sharma --- Change in v2: -Change in subject -Change in log message drivers/staging/typec/tcpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/typec/tcpm.c

[PATCH v2] staging: typec: tcpm: Comparison to NULL pointer

Makes code more concise and readable Signed-off-by: Harsha Sharma --- Change in v2: -Change in subject -Change in log message drivers/staging/typec/tcpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/typec/tcpm.c b/drivers/staging/typec/tcpm.c index

Re: [PATCH resend v2] power: supply: bq27xxx: enable writing capacity values for bq27421

On Friday 08 September 2017 19:38:37 H. Nikolaus Schaller wrote: > and here is the result: > > > root@letux:~# dmesg|fgrep bq27 > > [ 10.391235] bq27xxx_battery_setup > > [ 10.391265] bq27xxx_battery_setup: dm_regs=bf0520e0 > > [ 10.393798] (NULL device *): hwmon: 'bq27500-1-0' is not a

Re: [PATCH resend v2] power: supply: bq27xxx: enable writing capacity values for bq27421

On Friday 08 September 2017 19:38:37 H. Nikolaus Schaller wrote: > and here is the result: > > > root@letux:~# dmesg|fgrep bq27 > > [ 10.391235] bq27xxx_battery_setup > > [ 10.391265] bq27xxx_battery_setup: dm_regs=bf0520e0 > > [ 10.393798] (NULL device *): hwmon: 'bq27500-1-0' is not a

Re: [RFC 0/2] backlight: pwm_bl: support linear brightness to human eye

Hi, On Fri, Sep 8, 2017 at 4:18 AM, Daniel Thompson wrote: > On 07/09/17 19:04, Doug Anderson wrote: >> I'd agree that I don't think we should land Enric's series as-is. >> ...but I think something has been missing from the discussion so far: >> the fact that the

Re: [RFC 0/2] backlight: pwm_bl: support linear brightness to human eye

Hi, On Fri, Sep 8, 2017 at 4:18 AM, Daniel Thompson wrote: > On 07/09/17 19:04, Doug Anderson wrote: >> I'd agree that I don't think we should land Enric's series as-is. >> ...but I think something has been missing from the discussion so far: >> the fact that the backlight driver doesn't

Re: [PATCH resend v2] power: supply: bq27xxx: enable writing capacity values for bq27421

Hi Liam, I finally continues testing on OpenPandora. > Am 31.08.2017 um 22:19 schrieb Liam Breck : > > Hi, > > This may be a fix that allows >0 input from DT, but won't try to > program the register since the first 3 fields aren't compatible: > > ... bq27500_dm_regs[] =

Re: [PATCH resend v2] power: supply: bq27xxx: enable writing capacity values for bq27421

Hi Liam, I finally continues testing on OpenPandora. > Am 31.08.2017 um 22:19 schrieb Liam Breck : > > Hi, > > This may be a fix that allows >0 input from DT, but won't try to > program the register since the first 3 fields aren't compatible: > > ... bq27500_dm_regs[] = { > ... >

RE: [PATCH RFC 5/5] Add KSZ8795 SPI driver

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Friday, September 08, 2017 2:26 AM > To: Tristram Ha - C24268 > Cc: and...@lunn.ch; muva...@gmail.com; nathan.leigh.con...@gmail.com; > vivien.dide...@savoirfairelinux.com; f.faine...@gmail.com; >

RE: [PATCH RFC 5/5] Add KSZ8795 SPI driver

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Friday, September 08, 2017 2:26 AM > To: Tristram Ha - C24268 > Cc: and...@lunn.ch; muva...@gmail.com; nathan.leigh.con...@gmail.com; > vivien.dide...@savoirfairelinux.com; f.faine...@gmail.com; >

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, Sep 8, 2017 at 1:25 PM, Linus Torvalds wrote: > On Fri, Sep 8, 2017 at 12:09 AM, Christoph Hellwig wrote: >> >> But yes, for the init-time integrity_read_file this is incorrect. >> It never tripped up, and I explicitly added the lockdep

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, Sep 8, 2017 at 1:25 PM, Linus Torvalds wrote: > On Fri, Sep 8, 2017 at 12:09 AM, Christoph Hellwig wrote: >> >> But yes, for the init-time integrity_read_file this is incorrect. >> It never tripped up, and I explicitly added the lockdep annotations >> so that anything would show up, and

[PATCH v3 01/20] mm: Dont assume page-table invariance during faults

From: Peter Zijlstra One of the side effects of speculating on faults (without holding mmap_sem) is that we can race with free_pgtables() and therefore we cannot assume the page-tables will stick around. Remove the reliance on the pte pointer. Signed-off-by: Peter

Re: [v3] HID: google: add google hammer HID driver

On Thu, Sep 07, 2017 at 04:37:43PM +0800, Wei-Ning Huang wrote: > From: Wei-Ning Huang > > Add Google hammer HID driver. This driver allow us to control hammer > keyboard backlights and support future features. Since current hid-core > logic does not allow us to specify

[PATCH v3 01/20] mm: Dont assume page-table invariance during faults

From: Peter Zijlstra One of the side effects of speculating on faults (without holding mmap_sem) is that we can race with free_pgtables() and therefore we cannot assume the page-tables will stick around. Remove the reliance on the pte pointer. Signed-off-by: Peter Zijlstra (Intel) ---

Re: [v3] HID: google: add google hammer HID driver

On Thu, Sep 07, 2017 at 04:37:43PM +0800, Wei-Ning Huang wrote: > From: Wei-Ning Huang > > Add Google hammer HID driver. This driver allow us to control hammer > keyboard backlights and support future features. Since current hid-core > logic does not allow us to specify different USB interface

[PATCH v3 00/20] Speculative page faults

This is a port on kernel 4.13 of the work done by Peter Zijlstra to handle page fault without holding the mm semaphore [1]. The idea is to try to handle user space page faults without holding the mmap_sem. This should allow better concurrency for massively threaded process since the page fault

[PATCH v3 00/20] Speculative page faults

This is a port on kernel 4.13 of the work done by Peter Zijlstra to handle page fault without holding the mm semaphore [1]. The idea is to try to handle user space page faults without holding the mmap_sem. This should allow better concurrency for massively threaded process since the page fault

Re: [PATCH 1/2] staging: typec: tcpm: Validate source and sink caps

On Fri, Sep 8, 2017 at 2:45 AM, Greg Kroah-Hartman wrote: > On Thu, Sep 07, 2017 at 06:22:13PM -0700, Badhri Jagan Sridharan wrote: >> The source and sink caps should follow the following rules. >> This patch validates whether the src_caps/snk_caps adheres >> to it. >>

Re: [PATCH 1/2] staging: typec: tcpm: Validate source and sink caps

On Fri, Sep 8, 2017 at 2:45 AM, Greg Kroah-Hartman wrote: > On Thu, Sep 07, 2017 at 06:22:13PM -0700, Badhri Jagan Sridharan wrote: >> The source and sink caps should follow the following rules. >> This patch validates whether the src_caps/snk_caps adheres >> to it. >> >> 6.4.1 Capabilities

Re: [PATCH] ARC: AXS10x: Add temporary quirk to reset ethernet IP

On 09/08/2017 10:14 AM, Eugeniy Paltsev wrote: On Wed, 2017-09-06 at 12:54 -0700, Vineet Gupta wrote: On 09/06/2017 11:21 AM, Eugeniy Paltsev wrote: DW ethernet controller on AXS10x hangs sometimes after SW reset, so add temporary quirk to reset DW ethernet controller IP core. This quirk can

Re: [PATCH] ARC: AXS10x: Add temporary quirk to reset ethernet IP

On 09/08/2017 10:14 AM, Eugeniy Paltsev wrote: On Wed, 2017-09-06 at 12:54 -0700, Vineet Gupta wrote: On 09/06/2017 11:21 AM, Eugeniy Paltsev wrote: DW ethernet controller on AXS10x hangs sometimes after SW reset, so add temporary quirk to reset DW ethernet controller IP core. This quirk can

Re: [PATCH 1/2] staging: typec: tcpm: Validate source and sink caps

Thanks for the comments. Replies inline. On Fri, Sep 8, 2017 at 2:34 AM, Dan Carpenter wrote: > On Thu, Sep 07, 2017 at 06:22:13PM -0700, Badhri Jagan Sridharan wrote: >> +static int tcpm_validate_caps(struct tcpm_port *port, const u32 *pdo, >> +

Re: [PATCH 1/2] staging: typec: tcpm: Validate source and sink caps

Thanks for the comments. Replies inline. On Fri, Sep 8, 2017 at 2:34 AM, Dan Carpenter wrote: > On Thu, Sep 07, 2017 at 06:22:13PM -0700, Badhri Jagan Sridharan wrote: >> +static int tcpm_validate_caps(struct tcpm_port *port, const u32 *pdo, >> + unsigned int nr_pdo) >>

Re: [PATCH 2/2] mm, memory_hotplug: remove timeout from __offline_memory

On 09/04/2017 10:21 AM, Michal Hocko wrote: > From: Michal Hocko > > We have a hardcoded 120s timeout after which the memory offline fails > basically since the hot remove has been introduced. This is essentially > a policy implemented in the kernel. Moreover there is no way to

Re: [PATCH 2/2] mm, memory_hotplug: remove timeout from __offline_memory

On 09/04/2017 10:21 AM, Michal Hocko wrote: > From: Michal Hocko > > We have a hardcoded 120s timeout after which the memory offline fails > basically since the hot remove has been introduced. This is essentially > a policy implemented in the kernel. Moreover there is no way to adjust > the

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

From: David Woodhouse Date: Fri, 08 Sep 2017 18:23:22 +0100 > I don't know that anyone's ever tried saying "show me the chapter and > verse of the documentation" Do you know why I brought this up? Because the person I am replying to told me that the syscall documentation

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

From: David Woodhouse Date: Fri, 08 Sep 2017 18:23:22 +0100 > I don't know that anyone's ever tried saying "show me the chapter and > verse of the documentation" Do you know why I brought this up? Because the person I am replying to told me that the syscall documentation should have suggested

Re: [PATCH 1/2] mm, memory_hotplug: do not fail offlining too early

On 09/04/2017 10:21 AM, Michal Hocko wrote: > From: Michal Hocko > > Memory offlining can fail just too eagerly under a heavy memory pressure. > > [ 5410.336792] page:ea22a646bd00 count:255 mapcount:252 > mapping:88ff926c9f38 index:0x3 > [ 5410.336809] flags:

Re: [PATCH 1/2] mm, memory_hotplug: do not fail offlining too early

On 09/04/2017 10:21 AM, Michal Hocko wrote: > From: Michal Hocko > > Memory offlining can fail just too eagerly under a heavy memory pressure. > > [ 5410.336792] page:ea22a646bd00 count:255 mapcount:252 > mapping:88ff926c9f38 index:0x3 > [ 5410.336809] flags:

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, Sep 8, 2017 at 12:09 AM, Christoph Hellwig wrote: > > But yes, for the init-time integrity_read_file this is incorrect. > It never tripped up, and I explicitly added the lockdep annotations > so that anything would show up, and it's been half a year since > I sent that

Re: [GIT PULL] Security subsystem updates for 4.14

On Fri, Sep 8, 2017 at 12:09 AM, Christoph Hellwig wrote: > > But yes, for the init-time integrity_read_file this is incorrect. > It never tripped up, and I explicitly added the lockdep annotations > so that anything would show up, and it's been half a year since > I sent that first RFC patch..

Re: [PATCH 00/14] Fix wrong %pF and %pS printk format specifier usages

On Fri, Sep 08, 2017 at 03:18:30PM +0900, Sergey Senozhatsky wrote: > if the addr is not in kernel .text, then try dereferencing it and check > if the dereferenced addr is in kernel .text. If it really is a function pointer, then we know that it is safe to dereference. But if it isn't, then maybe

Re: [PATCH 00/14] Fix wrong %pF and %pS printk format specifier usages

On Fri, Sep 08, 2017 at 03:18:30PM +0900, Sergey Senozhatsky wrote: > if the addr is not in kernel .text, then try dereferencing it and check > if the dereferenced addr is in kernel .text. If it really is a function pointer, then we know that it is safe to dereference. But if it isn't, then maybe

Re: [PATCH v6 05/11] arm64/mm: Add support for XPFO

On Fri, Sep 08, 2017 at 12:53:47AM -0700, Christoph Hellwig wrote: > > +/* > > + * Lookup the page table entry for a virtual address and return a pointer > > to > > + * the entry. Based on x86 tree. > > + */ > > +static pte_t *lookup_address(unsigned long addr) > > Seems like this should be

Re: [PATCH v6 05/11] arm64/mm: Add support for XPFO

On Fri, Sep 08, 2017 at 12:53:47AM -0700, Christoph Hellwig wrote: > > +/* > > + * Lookup the page table entry for a virtual address and return a pointer > > to > > + * the entry. Based on x86 tree. > > + */ > > +static pte_t *lookup_address(unsigned long addr) > > Seems like this should be

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

On Fri, 2017-09-08 at 10:16 -0700, David Miller wrote: > From: Eduardo Valentin > Date: Fri, 8 Sep 2017 10:04:09 -0700 > > > > > However, this is a clear, the system call, from the net subsystem, > > has changed in behavior across kernel versions. From application / > >

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

On Fri, 2017-09-08 at 10:16 -0700, David Miller wrote: > From: Eduardo Valentin > Date: Fri, 8 Sep 2017 10:04:09 -0700 > > > > > However, this is a clear, the system call, from the net subsystem, > > has changed in behavior across kernel versions. From application / > > userspace perspective,

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

On Thu, Sep 7, 2017 at 11:18 PM, Masahiro Yamada wrote: > > If CONFIG_MODVERSIONS is enabled, > I notice lots of error messages. > WARNING: EXPORT symbol "finish_open" [vmlinux] version generation > failed, symbol will not be versioned > > So, I think something was

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

On Thu, Sep 7, 2017 at 11:18 PM, Masahiro Yamada wrote: > > If CONFIG_MODVERSIONS is enabled, > I notice lots of error messages. > WARNING: EXPORT symbol "finish_open" [vmlinux] version generation > failed, symbol will not be versioned > > So, I think something was broken in scripts/genksyms/. >

Re: WARNING: CPU: 2 PID: 4277 at lib/refcount.c:186

(Cc'ing netdev) On Fri, Sep 8, 2017 at 5:59 AM, Shankara Pailoor wrote: > Hi, > > I found a warning while fuzzing with Syzkaller on linux 4.13-rc7 on > x86_64. The full stack trace is below: > > WARNING: CPU: 2 PID: 4277 at lib/refcount.c:186 >

Re: WARNING: CPU: 2 PID: 4277 at lib/refcount.c:186

(Cc'ing netdev) On Fri, Sep 8, 2017 at 5:59 AM, Shankara Pailoor wrote: > Hi, > > I found a warning while fuzzing with Syzkaller on linux 4.13-rc7 on > x86_64. The full stack trace is below: > > WARNING: CPU: 2 PID: 4277 at lib/refcount.c:186 > refcount_sub_and_test+0x167/0x1b0

[PATCH v3 3/3] interconnect: Add Qualcomm msm8916 interconnect provider driver

Add driver for the Qualcomm interconnect buses found in msm8916 based platforms. This patch contains only a partial topology to make reviewing easier. Signed-off-by: Georgi Djakov --- drivers/interconnect/Kconfig | 5 +

[PATCH v3 3/3] interconnect: Add Qualcomm msm8916 interconnect provider driver

Add driver for the Qualcomm interconnect buses found in msm8916 based platforms. This patch contains only a partial topology to make reviewing easier. Signed-off-by: Georgi Djakov --- drivers/interconnect/Kconfig | 5 + drivers/interconnect/Makefile|

[RFC v3 2/3] interconnect: Add basic event tracing

Add basic tracepoints in interconnect_set() so we can trace the performance and the operations which configure the hardware. Signed-off-by: Georgi Djakov Cc: Steven Rostedt Cc: Ingo Molnar --- drivers/interconnect/interconnect.c

[RFC v3 2/3] interconnect: Add basic event tracing

Add basic tracepoints in interconnect_set() so we can trace the performance and the operations which configure the hardware. Signed-off-by: Georgi Djakov Cc: Steven Rostedt Cc: Ingo Molnar --- drivers/interconnect/interconnect.c | 7 ++ include/trace/events/interconnect.h | 45

[PATCH v3 0/3] Introduce on-chip interconnect API

Modern SoCs have multiple processors and various dedicated cores (video, gpu, graphics, modem). These cores are talking to each other and can generate a lot of data flowing through the on-chip interconnects. These interconnect buses could form different topologies such as crossbar, point to point

[PATCH v3 0/3] Introduce on-chip interconnect API

Modern SoCs have multiple processors and various dedicated cores (video, gpu, graphics, modem). These cores are talking to each other and can generate a lot of data flowing through the on-chip interconnects. These interconnect buses could form different topologies such as crossbar, point to point

[PATCH v3 1/3] interconnect: Add generic on-chip interconnect API

This patch introduce a new API to get requirements and configure the interconnect buses across the entire chipset to fit with the current demand. The API is using a consumer/provider-based model, where the providers are the interconnect buses and the consumers could be various drivers. The

Re: XFS mounted with 'discard' option - deleting fio test files slow

Adding amazon-linux-ker...@amazon.com On 9/7/17, 11:22 AM, "Lu, Qian" wrote: Hi XFS mailing list, Recently we received a bug report in the XFS filesystem with 'discard' option. I have been able to reproduce this issue. I used XFS filesystem to format NVMe SSD

[PATCH v3 1/3] interconnect: Add generic on-chip interconnect API

This patch introduce a new API to get requirements and configure the interconnect buses across the entire chipset to fit with the current demand. The API is using a consumer/provider-based model, where the providers are the interconnect buses and the consumers could be various drivers. The

Re: XFS mounted with 'discard' option - deleting fio test files slow

Adding amazon-linux-ker...@amazon.com On 9/7/17, 11:22 AM, "Lu, Qian" wrote: Hi XFS mailing list, Recently we received a bug report in the XFS filesystem with 'discard' option. I have been able to reproduce this issue. I used XFS filesystem to format NVMe SSD and mounted with

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

From: Eduardo Valentin Date: Fri, 8 Sep 2017 10:04:09 -0700 > However, this is a clear, the system call, from the net subsystem, > has changed in behavior across kernel versions. From application / > userspace perspective, changing the system call without clear > documentation

Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket

From: Eduardo Valentin Date: Fri, 8 Sep 2017 10:04:09 -0700 > However, this is a clear, the system call, from the net subsystem, > has changed in behavior across kernel versions. From application / > userspace perspective, changing the system call without clear > documentation or deprecation

<    1   2   3   4   5   6   7   8   9   10   >