Re: [PATCH v2 1/2] ARM: davinci: Allocate extra interrupts

On 02/02/2017 09:06 AM, Sekhar Nori wrote: On Friday 20 January 2017 11:47 PM, David Lechner wrote: On 01/20/2017 05:50 AM, Sekhar Nori wrote: On Wednesday 18 January 2017 10:27 PM, David Lechner wrote: On 01/18/2017 03:50 AM, Sekhar Nori wrote: On Saturday 14 January 2017 01:30 AM, David

RE: [PATCH] scsi: aacraid: avoid open-coded upper_32_bits

> -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Tuesday, February 7, 2017 5:00 AM > To: dl-esc-Aacraid Linux Driver ; James E.J. > Bottomley ; Martin K. Petersen > > Cc: Arnd Bergmann

Re: [PATCH v2 1/2] ARM: davinci: Allocate extra interrupts

On 02/02/2017 09:06 AM, Sekhar Nori wrote: On Friday 20 January 2017 11:47 PM, David Lechner wrote: On 01/20/2017 05:50 AM, Sekhar Nori wrote: On Wednesday 18 January 2017 10:27 PM, David Lechner wrote: On 01/18/2017 03:50 AM, Sekhar Nori wrote: On Saturday 14 January 2017 01:30 AM, David

RE: [PATCH] scsi: aacraid: avoid open-coded upper_32_bits

> -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Tuesday, February 7, 2017 5:00 AM > To: dl-esc-Aacraid Linux Driver ; James E.J. > Bottomley ; Martin K. Petersen > > Cc: Arnd Bergmann ; Johannes Thumshirn > ; Raghava Aditya Renukunta > ; Dave Carroll > ;

[PATCH 00/18] HID: Fine-tuning for several function implementations

From: Markus Elfring Date: Tue, 7 Feb 2017 20:26:54 +0100 Several update suggestions were taken into account from static source code analysis. Markus Elfring (18): Use kmalloc_array() in hid_input_field() Delete an error message for a failed memory allocation

[PATCH 00/18] HID: Fine-tuning for several function implementations

From: Markus Elfring Date: Tue, 7 Feb 2017 20:26:54 +0100 Several update suggestions were taken into account from static source code analysis. Markus Elfring (18): Use kmalloc_array() in hid_input_field() Delete an error message for a failed memory allocation in open_collection() Use

RE: [PATCH][V2] scsi: aacraid: rcode is unsigned and should be signed int

> -Original Message- > From: Colin King [mailto:colin.k...@canonical.com] > Sent: Tuesday, February 7, 2017 3:51 AM > To: dl-esc-Aacraid Linux Driver ; James E . J . > Bottomley ; Martin K . Petersen > ;

RE: [PATCH][V2] scsi: aacraid: rcode is unsigned and should be signed int

> -Original Message- > From: Colin King [mailto:colin.k...@canonical.com] > Sent: Tuesday, February 7, 2017 3:51 AM > To: dl-esc-Aacraid Linux Driver ; James E . J . > Bottomley ; Martin K . Petersen > ; linux-s...@vger.kernel.org > Cc: kernel-janit...@vger.kernel.org;

Re: [PATCH RESEND] [media] usbtv: add a new usbid

On Wed, 2017-02-08 at 02:43 +0800, Icenowy Zheng wrote: > A new usbid of UTV007 is found in a newly bought device. > > The usbid is 1f71:3301. > > The ID on the chip is: > UTV007 > A89029.1 > 1520L18K1 > > Both video and audio is tested with the modified usbtv driver. > > Signed-off-by:

Re: [PATCH RESEND] [media] usbtv: add a new usbid

On Wed, 2017-02-08 at 02:43 +0800, Icenowy Zheng wrote: > A new usbid of UTV007 is found in a newly bought device. > > The usbid is 1f71:3301. > > The ID on the chip is: > UTV007 > A89029.1 > 1520L18K1 > > Both video and audio is tested with the modified usbtv driver. > > Signed-off-by:

Re: [PATCH v8 2/5] mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available

Am 10.01.2017 um 20:30 schrieb Zach Brown: > From: Jeff Westfahl > > If the user has not set max_beb_per1024 using either the cmdline or > Kconfig options for doing so, use the MTD function 'max_bad_blocks' to > compute the UBI bad_peb_limit. > > Signed-off-by: Jeff

Re: [PATCH v8 2/5] mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available

Am 10.01.2017 um 20:30 schrieb Zach Brown: > From: Jeff Westfahl > > If the user has not set max_beb_per1024 using either the cmdline or > Kconfig options for doing so, use the MTD function 'max_bad_blocks' to > compute the UBI bad_peb_limit. > > Signed-off-by: Jeff Westfahl > Signed-off-by:

Re: arch: Rename CONFIG_DEBUG_RODATA and CONFIG_DEBUG_MODULE_RONX

+++ Laura Abbott [06/02/17 16:31 -0800]: Both of these options are poorly named. The features they provide are necessary for system security and should not be considered debug only. Change the names to CONFIG_STRICT_KERNEL_RWX and CONFIG_STRICT_MODULE_RWX to better describe what these options

Re: arch: Rename CONFIG_DEBUG_RODATA and CONFIG_DEBUG_MODULE_RONX

+++ Laura Abbott [06/02/17 16:31 -0800]: Both of these options are poorly named. The features they provide are necessary for system security and should not be considered debug only. Change the names to CONFIG_STRICT_KERNEL_RWX and CONFIG_STRICT_MODULE_RWX to better describe what these options

Re: [PATCH] arm64: uaccess: consistently check object sizes

On Tue, Feb 7, 2017 at 10:52 AM, Mark Rutland wrote: > On Tue, Feb 07, 2017 at 10:27:52AM -0800, Kees Cook wrote: >> On Tue, Feb 7, 2017 at 4:33 AM, Mark Rutland wrote: >> > Currently in arm64's copy_{to,from}_user, we only check the >> >

Re: [PATCH] arm64: uaccess: consistently check object sizes

On Tue, Feb 7, 2017 at 10:52 AM, Mark Rutland wrote: > On Tue, Feb 07, 2017 at 10:27:52AM -0800, Kees Cook wrote: >> On Tue, Feb 7, 2017 at 4:33 AM, Mark Rutland wrote: >> > Currently in arm64's copy_{to,from}_user, we only check the >> > source/destination object size if access_ok() tells us

[PATCH] mm: fix KPF_SWAPCACHE

4.10-rc1 commit 6326fec1122c ("mm: Use owner_priv bit for PageSwapCache, valid when PageSwapBacked") aliased PG_swapcache to PG_owner_priv_1: so /proc/kpageflags' KPF_SWAPCACHE should now be synthesized, instead of being shown on unrelated pages which have PG_owner_priv_1 set. Signed-off-by: Hugh

Re: [PATCHv2] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Wed, Jan 25, 2017 at 07:30:32PM +0100, Jean-Jacques Hiblot wrote: > Abel, I tested it partially. OK, so I managed to find exactly what is happening. > It's seems OK if I have FRAME_POINTER enabled and it breaks otherwise. FRAME_POINTER is needed by OLD_MCOUNT. OLD_MCOUNT is needed by

[PATCH] mm: fix KPF_SWAPCACHE

4.10-rc1 commit 6326fec1122c ("mm: Use owner_priv bit for PageSwapCache, valid when PageSwapBacked") aliased PG_swapcache to PG_owner_priv_1: so /proc/kpageflags' KPF_SWAPCACHE should now be synthesized, instead of being shown on unrelated pages which have PG_owner_priv_1 set. Signed-off-by: Hugh

Re: [PATCHv2] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Wed, Jan 25, 2017 at 07:30:32PM +0100, Jean-Jacques Hiblot wrote: > Abel, I tested it partially. OK, so I managed to find exactly what is happening. > It's seems OK if I have FRAME_POINTER enabled and it breaks otherwise. FRAME_POINTER is needed by OLD_MCOUNT. OLD_MCOUNT is needed by

Re: [PATCH][net-next] net: bridge: remove redundant check to see if err is set

From: Colin King Date: Tue, 7 Feb 2017 10:56:38 + > From: Colin Ian King > > The error check on err is redundant as it is being checked > previously each time it has been updated. Remove this redundant > check. > > Detected with

Re: [PATCH][net-next] net: bridge: remove redundant check to see if err is set

From: Colin King Date: Tue, 7 Feb 2017 10:56:38 + > From: Colin Ian King > > The error check on err is redundant as it is being checked > previously each time it has been updated. Remove this redundant > check. > > Detected with CoverityScan, CID#140030("Logically dead code") > >

[PATCH] staging: comedi: Fix incorrect type assignment

This patch fixes the following sparse error: drivers/staging/comedi/drivers//ni_pcimio.c:1229:32: warning: incorrect type in assignment (different base types) drivers/staging/comedi/drivers//ni_pcimio.c:1229:32:expected restricted __be32 [usertype] serial_number

[PATCH] staging: comedi: Fix incorrect type assignment

This patch fixes the following sparse error: drivers/staging/comedi/drivers//ni_pcimio.c:1229:32: warning: incorrect type in assignment (different base types) drivers/staging/comedi/drivers//ni_pcimio.c:1229:32:expected restricted __be32 [usertype] serial_number

Re: [PATCH] staging: vc04_services: remove unused functions

On Tue, Feb 07, 2017 at 03:09:44PM +0300, Dan Carpenter wrote: > There is a bunch of vc04_services that we're still looking to merge in > the near future. Please hold off deleting these until we are further > along on that. > OK. Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu

Re: [PATCH] staging: vc04_services: remove unused functions

On Tue, Feb 07, 2017 at 03:09:44PM +0300, Dan Carpenter wrote: > There is a bunch of vc04_services that we're still looking to merge in > the near future. Please hold off deleting these until we are further > along on that. > OK. Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu

Re: memfill

On Mon, 2017-02-06 at 06:49 -0800, Matthew Wilcox wrote: > [adding linux-arch to see if anyone there wants to do an optimised > version of memfill for their CPU] > > On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote: > > +static inline void zram_fill_page(char *ptr, unsigned long len, >

Re: memfill

On Mon, 2017-02-06 at 06:49 -0800, Matthew Wilcox wrote: > [adding linux-arch to see if anyone there wants to do an optimised > version of memfill for their CPU] > > On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote: > > +static inline void zram_fill_page(char *ptr, unsigned long len, >

Re: [RFC][PATCH 1/2] remoteproc: Reduce asynchronous request_firmware to auto-boot only

Hi Bjorn, On 02/06/2017 01:08 PM, Bjorn Andersson wrote: On Tue 24 Jan 15:13 PST 2017, Sarangdhar Joshi wrote: The rproc_add_virtio_devices() requests firmware asynchronously and triggers boot if the auto_boot flag is set. However, this asynchronous call seems to be redundant for non

Re: [RFC][PATCH 1/2] remoteproc: Reduce asynchronous request_firmware to auto-boot only

Hi Bjorn, On 02/06/2017 01:08 PM, Bjorn Andersson wrote: On Tue 24 Jan 15:13 PST 2017, Sarangdhar Joshi wrote: The rproc_add_virtio_devices() requests firmware asynchronously and triggers boot if the auto_boot flag is set. However, this asynchronous call seems to be redundant for non

Re: memfill

On Tue, Feb 07, 2017 at 05:29:15PM +, David Howells wrote: > Matthew Wilcox wrote: > > > You've misunderstood the purpose of memfill. memfill allows the caller > > to specify a pattern which is not a single byte in size, eg memfill(addr, > > 0x12345678, 64) would result

Re: [PATCH] arm64: uaccess: consistently check object sizes

On Tue, Feb 07, 2017 at 10:27:52AM -0800, Kees Cook wrote: > On Tue, Feb 7, 2017 at 4:33 AM, Mark Rutland wrote: > > Currently in arm64's copy_{to,from}_user, we only check the > > source/destination object size if access_ok() tells us the user access > > is permissible. > >

Re: memfill

On Tue, Feb 07, 2017 at 05:29:15PM +, David Howells wrote: > Matthew Wilcox wrote: > > > You've misunderstood the purpose of memfill. memfill allows the caller > > to specify a pattern which is not a single byte in size, eg memfill(addr, > > 0x12345678, 64) would result in 0x12345678 being

Re: [PATCH] arm64: uaccess: consistently check object sizes

On Tue, Feb 07, 2017 at 10:27:52AM -0800, Kees Cook wrote: > On Tue, Feb 7, 2017 at 4:33 AM, Mark Rutland wrote: > > Currently in arm64's copy_{to,from}_user, we only check the > > source/destination object size if access_ok() tells us the user access > > is permissible. > > > > However, in

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Tue, Feb 07, 2017 at 12:08:09AM -0800, Stephane Eranian wrote: > Hi, > > I wanted to take a few steps back and look at the overall goals for > cache monitoring. > From the various threads and discussion, my understanding is as follows. > > I think the design must ensure that the following

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Tue, Feb 07, 2017 at 12:08:09AM -0800, Stephane Eranian wrote: > Hi, > > I wanted to take a few steps back and look at the overall goals for > cache monitoring. > From the various threads and discussion, my understanding is as follows. > > I think the design must ensure that the following

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, 2017-02-07 at 10:10 -0800, Christoph Hellwig wrote: > On Tue, Feb 07, 2017 at 07:59:00PM +0200, Amir Goldstein wrote: > > I am not even sure that would be enough. > > dentry does not contain information about the mount user came from, > > and sb contains only information about the user ns

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, 2017-02-07 at 10:10 -0800, Christoph Hellwig wrote: > On Tue, Feb 07, 2017 at 07:59:00PM +0200, Amir Goldstein wrote: > > I am not even sure that would be enough. > > dentry does not contain information about the mount user came from, > > and sb contains only information about the user ns

Re: [PATCH v2 1/2] sierra_net: Add support for IPv6 and Dual-Stack Link Sense Indications

From: Stefan Brüns Date: Tue, 7 Feb 2017 03:33:16 +0100 > If a context is configured as dualstack ("IPv4v6"), the modem indicates > the context activation with a slightly different indication message. > The dual-stack indication omits the link_type (IPv4/v6) and

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Mon, 2017-02-06 at 20:35 -0500, J. Bruce Fields wrote: > On Mon, Feb 06, 2017 at 04:10:11PM -0800, James Bottomley wrote: > > On Mon, 2017-02-06 at 16:52 -0500, J. Bruce Fields wrote: > > > On Mon, Feb 06, 2017 at 07:18:16AM -0800, James Bottomley wrote: > > > > On Mon, 2017-02-06 at 09:50

Re: [PATCH v2 1/2] sierra_net: Add support for IPv6 and Dual-Stack Link Sense Indications

From: Stefan Brüns Date: Tue, 7 Feb 2017 03:33:16 +0100 > If a context is configured as dualstack ("IPv4v6"), the modem indicates > the context activation with a slightly different indication message. > The dual-stack indication omits the link_type (IPv4/v6) and adds > additional address fields.

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Mon, 2017-02-06 at 20:35 -0500, J. Bruce Fields wrote: > On Mon, Feb 06, 2017 at 04:10:11PM -0800, James Bottomley wrote: > > On Mon, 2017-02-06 at 16:52 -0500, J. Bruce Fields wrote: > > > On Mon, Feb 06, 2017 at 07:18:16AM -0800, James Bottomley wrote: > > > > On Mon, 2017-02-06 at 09:50

Re: [PATCH v2 2/2] sierra_net: Skip validating irrelevant fields for IDLE LSIs

From: Stefan Brüns Date: Tue, 7 Feb 2017 03:33:17 +0100 > When the context is deactivated, the link_type is set to 0xff, which > triggers a warning message, and results in a wrong link status, as > the LSI is ignored. > > Signed-off-by: Stefan Brüns

Re: [PATCH v2 2/2] sierra_net: Skip validating irrelevant fields for IDLE LSIs

From: Stefan Brüns Date: Tue, 7 Feb 2017 03:33:17 +0100 > When the context is deactivated, the link_type is set to 0xff, which > triggers a warning message, and results in a wrong link status, as > the LSI is ignored. > > Signed-off-by: Stefan Brüns Applied.

Re: [PATCH v3 2/3] net: phy: dp83867: Add lane swapping support in the DP83867 TI's PHY driver

From: Lukasz Majewski Date: Tue, 7 Feb 2017 06:20:23 +0100 > This patch adds support for enabling or disabling the lane swapping (called > "port mirroring" in PHY's CFG4 register) feature of the DP83867 TI's PHY > device. > > One use case is when bootstrap configuration enables

Re: [PATCH v3 2/3] net: phy: dp83867: Add lane swapping support in the DP83867 TI's PHY driver

From: Lukasz Majewski Date: Tue, 7 Feb 2017 06:20:23 +0100 > This patch adds support for enabling or disabling the lane swapping (called > "port mirroring" in PHY's CFG4 register) feature of the DP83867 TI's PHY > device. > > One use case is when bootstrap configuration enables this feature

Re: [PATCH v3 1/3] Documentation: devicetree: Add PHY no lane swap binding

From: Lukasz Majewski Date: Tue, 7 Feb 2017 06:21:34 +0100 > Add the documentation to avoid PHY lane swapping. This is a boolean > entry to notify the phy device drivers that the TX/RX lanes NO need > to be swapped. > The use case for this binding mostly happens after wrong HW >

Re: [PATCH v3 1/3] Documentation: devicetree: Add PHY no lane swap binding

From: Lukasz Majewski Date: Tue, 7 Feb 2017 06:21:34 +0100 > Add the documentation to avoid PHY lane swapping. This is a boolean > entry to notify the phy device drivers that the TX/RX lanes NO need > to be swapped. > The use case for this binding mostly happens after wrong HW > configuration

Re: [PATCH v3 3/3] net: phy: dp83867: Recover from "port mirroring" N/A MODE4

From: Lukasz Majewski Date: Tue, 7 Feb 2017 06:20:24 +0100 > The DP83867 when not properly bootstrapped - especially with LED_0 pin - > can enter N/A MODE4 for "port mirroring" feature. > > To provide normal operation of the PHY, one needs not only to explicitly > disable the

Re: [PATCH v3 3/3] net: phy: dp83867: Recover from "port mirroring" N/A MODE4

From: Lukasz Majewski Date: Tue, 7 Feb 2017 06:20:24 +0100 > The DP83867 when not properly bootstrapped - especially with LED_0 pin - > can enter N/A MODE4 for "port mirroring" feature. > > To provide normal operation of the PHY, one needs not only to explicitly > disable the port mirroring

[PATCH] xen-netfront: Rework the fix for Rx stall during OOM and network stress

The commit 90c311b0eeea ("xen-netfront: Fix Rx stall during network stress and OOM") caused the refill timer to be triggerred almost on all invocations of xennet_alloc_rx_buffers for certain workloads. This reworks the fix by reverting to the old behaviour and taking into consideration the skb

[PATCH] xen-netfront: Rework the fix for Rx stall during OOM and network stress

The commit 90c311b0eeea ("xen-netfront: Fix Rx stall during network stress and OOM") caused the refill timer to be triggerred almost on all invocations of xennet_alloc_rx_buffers for certain workloads. This reworks the fix by reverting to the old behaviour and taking into consideration the skb

Re: [PATCH] Documentation: powerpc/fsl: Update compatible for l2cache binding

On Fri, Feb 03, 2017 at 01:43:16PM +1300, Chris Packham wrote: > List all the current valid compatible strings for the l2cache binding. > This should stop checkpatch.pl from complaining and will hopefully save > someone from having to debug a typo in their dts. > > Signed-off-by: Chris Packham

Re: [PATCH] Documentation: powerpc/fsl: Update compatible for l2cache binding

On Fri, Feb 03, 2017 at 01:43:16PM +1300, Chris Packham wrote: > List all the current valid compatible strings for the l2cache binding. > This should stop checkpatch.pl from complaining and will hopefully save > someone from having to debug a typo in their dts. > > Signed-off-by: Chris Packham >

Re: [PATCH net-next 0/4] net: Incorrect use of phy_read_status()

From: Florian Fainelli Date: Mon, 6 Feb 2017 15:55:19 -0800 > This patch series removes incorrect uses of phy_read_status() which can > clobber > the PHY device link while we are executing with the state machine running. > > greth was potentially another candidate, but

Re: [PATCH net-next 0/4] net: Incorrect use of phy_read_status()

From: Florian Fainelli Date: Mon, 6 Feb 2017 15:55:19 -0800 > This patch series removes incorrect uses of phy_read_status() which can > clobber > the PHY device link while we are executing with the state machine running. > > greth was potentially another candidate, but it does funky stuff

Re: [PATCH v2 1/2] sierra_net: Add support for IPv6 and Dual-Stack Link Sense Indications

From: David Miller Date: Tue, 07 Feb 2017 13:53:12 -0500 (EST) > From: Stefan Brüns > Date: Tue, 7 Feb 2017 03:33:16 +0100 > >> If a context is configured as dualstack ("IPv4v6"), the modem indicates >> the context activation with a slightly

Re: [PATCH v2 1/2] sierra_net: Add support for IPv6 and Dual-Stack Link Sense Indications

From: David Miller Date: Tue, 07 Feb 2017 13:53:12 -0500 (EST) > From: Stefan Brüns > Date: Tue, 7 Feb 2017 03:33:16 +0100 > >> If a context is configured as dualstack ("IPv4v6"), the modem indicates >> the context activation with a slightly different indication message. >> The dual-stack

Re: [GIT PULL] cputime: Convert core use of cputime_t to nsecs

* Frederic Weisbecker wrote: > On Tue, Feb 07, 2017 at 09:08:18AM +0100, Ingo Molnar wrote: > > > > * Frederic Weisbecker wrote: > > > > > On Mon, Jan 30, 2017 at 05:46:43AM +0100, Frederic Weisbecker wrote: > > > > Ingo, > > > > > > > > Please pull

Re: [GIT PULL] cputime: Convert core use of cputime_t to nsecs

* Frederic Weisbecker wrote: > On Tue, Feb 07, 2017 at 09:08:18AM +0100, Ingo Molnar wrote: > > > > * Frederic Weisbecker wrote: > > > > > On Mon, Jan 30, 2017 at 05:46:43AM +0100, Frederic Weisbecker wrote: > > > > Ingo, > > > > > > > > Please pull the cputime/nsecs-for-tip branch that can

[PATCH] leds: pca9532: Extend pca9532 device tree support

This patch extends the device tree support for the pca9532 allowing LEDs to blink, dim or even being unchanged, i.e. not being turned off during driver initialization. Signed-off-by: Felix Brack --- .../devicetree/bindings/leds/leds-pca9532.txt | 22

[PATCH] leds: pca9532: Extend pca9532 device tree support

This patch extends the device tree support for the pca9532 allowing LEDs to blink, dim or even being unchanged, i.e. not being turned off during driver initialization. Signed-off-by: Felix Brack --- .../devicetree/bindings/leds/leds-pca9532.txt | 22

Re: [PATCH net-next v2 1/8] bpf: Use bpf_load_program() from the library

Please post your patch series(s) with proper "[PATCH ... 0/N]" header postings. Thank you.

Re: [PATCH v6 1/2] dt-bindings: brcm: clocks: add binding for brcmstb-cpu-clk-div

On Wed, Feb 01, 2017 at 03:26:37PM -0800, Markus Mayer wrote: > From: Markus Mayer > > Add binding document for brcm,brcmstb-cpu-clk-div. > > Signed-off-by: Markus Mayer > --- > .../bindings/clock/brcm,brcmstb-cpu-clk-div.txt| 22 >

Re: [PATCH net-next v2 1/8] bpf: Use bpf_load_program() from the library

Please post your patch series(s) with proper "[PATCH ... 0/N]" header postings. Thank you.

Re: [PATCH v6 1/2] dt-bindings: brcm: clocks: add binding for brcmstb-cpu-clk-div

On Wed, Feb 01, 2017 at 03:26:37PM -0800, Markus Mayer wrote: > From: Markus Mayer > > Add binding document for brcm,brcmstb-cpu-clk-div. > > Signed-off-by: Markus Mayer > --- > .../bindings/clock/brcm,brcmstb-cpu-clk-div.txt| 22 > ++ > MAINTAINERS

Re: [PATCH] net: ethernet: ti: cpsw: remove netif_trans_update

From: Ivan Khoronzhuk Date: Tue, 7 Feb 2017 00:53:45 +0200 > No need to update jiffies in txq->trans_start twice, it's supposed to be > done in netdev_start_xmit() and anyway is re-written. Also, no reason to > update trans time in case of an error. > >

Re: [PATCH] net: ethernet: ti: cpsw: remove netif_trans_update

From: Ivan Khoronzhuk Date: Tue, 7 Feb 2017 00:53:45 +0200 > No need to update jiffies in txq->trans_start twice, it's supposed to be > done in netdev_start_xmit() and anyway is re-written. Also, no reason to > update trans time in case of an error. > > Signed-off-by: Ivan Khoronzhuk > --- >

Re: [PATCH v10] perf: add qcom l2 cache perf events driver

Hi Neil, On Tue, Feb 07, 2017 at 01:14:04PM -0500, Neil Leeder wrote: > Adds perf events support for L2 cache PMU. > > The L2 cache PMU driver is named 'l2cache_0' and can be used > with perf events to profile L2 events such as cache hits > and misses on Qualcomm Technologies processors. > >

Re: [PATCH v10] perf: add qcom l2 cache perf events driver

Hi Neil, On Tue, Feb 07, 2017 at 01:14:04PM -0500, Neil Leeder wrote: > Adds perf events support for L2 cache PMU. > > The L2 cache PMU driver is named 'l2cache_0' and can be used > with perf events to profile L2 events such as cache hits > and misses on Qualcomm Technologies processors. > >

Re: [PATCHv4 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces

From: Sainath Grandhi Date: Mon, 6 Feb 2017 13:36:08 -0800 > Tap character devices can be implemented on other virtual interfaces like > ipvlan, similar to macvtap. Source code for tap functionality in macvtap > can be re-used for this purpose. > > This patch series

Re: [PATCHv4 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces

From: Sainath Grandhi Date: Mon, 6 Feb 2017 13:36:08 -0800 > Tap character devices can be implemented on other virtual interfaces like > ipvlan, similar to macvtap. Source code for tap functionality in macvtap > can be re-used for this purpose. > > This patch series splits macvtap source into

Re: [PATCH] arm64: uaccess: consistently check object sizes

On Tue, Feb 7, 2017 at 4:33 AM, Mark Rutland wrote: > Currently in arm64's copy_{to,from}_user, we only check the > source/destination object size if access_ok() tells us the user access > is permissible. > > However, in copy_from_user() we'll subsequently zero any remainder

Re: [PATCH] arm64: uaccess: consistently check object sizes

On Tue, Feb 7, 2017 at 4:33 AM, Mark Rutland wrote: > Currently in arm64's copy_{to,from}_user, we only check the > source/destination object size if access_ok() tells us the user access > is permissible. > > However, in copy_from_user() we'll subsequently zero any remainder on > the destination

Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure

On 2 February 2017 at 09:22, Alexander Shishkin wrote: > Mathieu Poirier writes: > >> If this is what you want to convey then >> >> + * @action:filter/start/stop >> >> needs to be fixed. This can be interpreted as "use range

Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure

On 2 February 2017 at 09:22, Alexander Shishkin wrote: > Mathieu Poirier writes: > >> If this is what you want to convey then >> >> + * @action:filter/start/stop >> >> needs to be fixed. This can be interpreted as "use range filter, >> start filter or stop filter" - which is exactly what I

Re: [PATCH 3/6] KVM: x86: preparatory changes for APICv cleanups

2016-12-19 17:17+0100, Paolo Bonzini: > Add return value to __kvm_apic_update_irr/kvm_apic_update_irr. > Move vmx_sync_pir_to_irr around. > > Signed-off-by: Paolo Bonzini > --- Reviewed-by: Radim Krčmář > arch/x86/kvm/lapic.c | 25

Re: [PATCH 3/6] KVM: x86: preparatory changes for APICv cleanups

2016-12-19 17:17+0100, Paolo Bonzini: > Add return value to __kvm_apic_update_irr/kvm_apic_update_irr. > Move vmx_sync_pir_to_irr around. > > Signed-off-by: Paolo Bonzini > --- Reviewed-by: Radim Krčmář > arch/x86/kvm/lapic.c | 25 + > arch/x86/kvm/lapic.h | 4 ++-- >

Re: [PATCH 08/10] ARM: davinci: fix the DT boot on da850-evm

Bartosz Golaszewski writes: > When we enable vpif capture on the da850-evm we hit a BUG_ON() because > the i2c adapter can't be found. The board file boot uses i2c adapter 1 > but in the DT mode it's actually adapter 0. Drop the problematic lines. > > Signed-off-by:

Re: [PATCH 10/10] ARM: davinci: add pdata-quirks for da850-evm vpif display

Bartosz Golaszewski writes: > Similarly to vpif capture: we need to register the vpif display driver > and the corresponding adv7343 encoder in pdata-quirks as the DT > support is not complete. To add a bit more detail to the changelog: DT support is not complete

Re: [PATCH 08/10] ARM: davinci: fix the DT boot on da850-evm

Bartosz Golaszewski writes: > When we enable vpif capture on the da850-evm we hit a BUG_ON() because > the i2c adapter can't be found. The board file boot uses i2c adapter 1 > but in the DT mode it's actually adapter 0. Drop the problematic lines. > > Signed-off-by: Bartosz Golaszewski > --- >

Re: [PATCH 10/10] ARM: davinci: add pdata-quirks for da850-evm vpif display

Bartosz Golaszewski writes: > Similarly to vpif capture: we need to register the vpif display driver > and the corresponding adv7343 encoder in pdata-quirks as the DT > support is not complete. To add a bit more detail to the changelog: DT support is not complete since there isn't currently a

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, 2017-02-07 at 19:59 +0200, Amir Goldstein wrote: > On Tue, Feb 7, 2017 at 6:37 PM, James Bottomley > wrote: > > On Tue, 2017-02-07 at 01:19 -0800, Christoph Hellwig wrote: > > > On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote: > > > >

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, 2017-02-07 at 19:59 +0200, Amir Goldstein wrote: > On Tue, Feb 7, 2017 at 6:37 PM, James Bottomley > wrote: > > On Tue, 2017-02-07 at 01:19 -0800, Christoph Hellwig wrote: > > > On Sat, Feb 04, 2017 at 11:19:32AM -0800, James Bottomley wrote: > > > > This allows any subtree to be uid/gid

Re: [PATCH v2 2/5] async_tx: Handle DMA devices having support for fewer PQ coefficients

On Tue, Feb 7, 2017 at 1:02 AM, Anup Patel wrote: > On Tue, Feb 7, 2017 at 1:57 PM, Dan Williams wrote: >> On Tue, Feb 7, 2017 at 12:16 AM, Anup Patel wrote: >>> The DMAENGINE framework assumes that if PQ offload is

Re: [PATCH v2 2/5] async_tx: Handle DMA devices having support for fewer PQ coefficients

On Tue, Feb 7, 2017 at 1:02 AM, Anup Patel wrote: > On Tue, Feb 7, 2017 at 1:57 PM, Dan Williams wrote: >> On Tue, Feb 7, 2017 at 12:16 AM, Anup Patel wrote: >>> The DMAENGINE framework assumes that if PQ offload is supported by a >>> DMA device then all 256 PQ coefficients are supported. This

Re: [PATCH 2/6] kvm: nVMX: move nested events check to kvm_vcpu_running

2016-12-19 17:17+0100, Paolo Bonzini: > vcpu_run calls kvm_vcpu_running, not kvm_arch_vcpu_runnable, > and the former does not call check_nested_events. > > Once KVM_REQ_EVENT is removed from the APICv interrupt injection > path, however, this would leave no place to trigger a vmexit > from L2 to

Re: [PATCH 2/6] kvm: nVMX: move nested events check to kvm_vcpu_running

2016-12-19 17:17+0100, Paolo Bonzini: > vcpu_run calls kvm_vcpu_running, not kvm_arch_vcpu_runnable, > and the former does not call check_nested_events. > > Once KVM_REQ_EVENT is removed from the APICv interrupt injection > path, however, this would leave no place to trigger a vmexit > from L2 to

Re: [PATCH 09/10] media: vpif: use a configurable i2c_adapter_id for vpif display

Bartosz Golaszewski writes: > The vpif display driver uses a static i2c adapter ID of 1 but on the > da850-evm board in DT boot mode the i2c adapter ID is actually 0. > > Make the adapter ID configurable like it already is for vpif capture. > > Signed-off-by: Bartosz

Re: [PATCH 09/10] media: vpif: use a configurable i2c_adapter_id for vpif display

Bartosz Golaszewski writes: > The vpif display driver uses a static i2c adapter ID of 1 but on the > da850-evm board in DT boot mode the i2c adapter ID is actually 0. > > Make the adapter ID configurable like it already is for vpif capture. > > Signed-off-by: Bartosz Golaszewski Acked-by:

[PATCH v10] perf: add qcom l2 cache perf events driver

Adds perf events support for L2 cache PMU. The L2 cache PMU driver is named 'l2cache_0' and can be used with perf events to profile L2 events such as cache hits and misses on Qualcomm Technologies processors. Signed-off-by: Neil Leeder --- v10: Remove unnecessary

[PATCH v10] perf: add qcom l2 cache perf events driver

Adds perf events support for L2 cache PMU. The L2 cache PMU driver is named 'l2cache_0' and can be used with perf events to profile L2 events such as cache hits and misses on Qualcomm Technologies processors. Signed-off-by: Neil Leeder --- v10: Remove unnecessary cross-call for reset Remove

Re: [PATCH] Input: pwm-beeper: support customized freq for SND_BELL

On Tue, Feb 07, 2017 at 06:21:34AM +0100, Heiko Schocher wrote: > From: Guan Ben > > extend the pwm-beeper driver to support customized frequency > for SND_BELL from device tree. No, SND_BELL is literally SND_TONE @1000Hz. There should be no customizing. If applications

Re: [PATCH] Input: pwm-beeper: support customized freq for SND_BELL

On Tue, Feb 07, 2017 at 06:21:34AM +0100, Heiko Schocher wrote: > From: Guan Ben > > extend the pwm-beeper driver to support customized frequency > for SND_BELL from device tree. No, SND_BELL is literally SND_TONE @1000Hz. There should be no customizing. If applications want to use different

Re: [RFC V2 12/12] mm: Tag VMA with VM_CDM flag explicitly during mbind(MPOL_BIND)

On 01/30/2017 08:36 PM, Anshuman Khandual wrote: > On 01/30/2017 11:24 PM, Dave Hansen wrote: >> On 01/29/2017 07:35 PM, Anshuman Khandual wrote: >>> + if ((new_pol->mode == MPOL_BIND) >>> + && nodemask_has_cdm(new_pol->v.nodes)) >>> + set_vm_cdm(vma);

Re: [RFC V2 12/12] mm: Tag VMA with VM_CDM flag explicitly during mbind(MPOL_BIND)

On 01/30/2017 08:36 PM, Anshuman Khandual wrote: > On 01/30/2017 11:24 PM, Dave Hansen wrote: >> On 01/29/2017 07:35 PM, Anshuman Khandual wrote: >>> + if ((new_pol->mode == MPOL_BIND) >>> + && nodemask_has_cdm(new_pol->v.nodes)) >>> + set_vm_cdm(vma);

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 07, 2017 at 07:59:00PM +0200, Amir Goldstein wrote: > I am not even sure that would be enough. > dentry does not contain information about the mount user came from, > and sb contains only information about the user ns of the mounter of > the file system, not the mounter of the bind

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 07, 2017 at 07:59:00PM +0200, Amir Goldstein wrote: > I am not even sure that would be enough. > dentry does not contain information about the mount user came from, > and sb contains only information about the user ns of the mounter of > the file system, not the mounter of the bind

[PATCH v2 1/4] ARM: pwm: sun4i: unification of register operations for support sun6i.

From: Siarhei Volkau This patch not introduce new features, just prepare code for adding sun6i PWM driver in next commits. A31 SoC have a different map of PWM registers than others ASoCs, but register bits purposes are very similar. This patch introduce set of register

[PATCH v2 1/4] ARM: pwm: sun4i: unification of register operations for support sun6i.

From: Siarhei Volkau This patch not introduce new features, just prepare code for adding sun6i PWM driver in next commits. A31 SoC have a different map of PWM registers than others ASoCs, but register bits purposes are very similar. This patch introduce set of register access routines, which

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