[PATCH net-next v2 01/10] net: dsa: add debugfs interface

This commit adds a DEBUG_FS dependent DSA core file creating a generic debug filesystem interface for the DSA switch devices. The interface can be mounted with: # mount -t debugfs none /sys/kernel/debug The dsa directory contains one directory per switch chip: # cd

[PATCH net-next v2 01/10] net: dsa: add debugfs interface

This commit adds a DEBUG_FS dependent DSA core file creating a generic debug filesystem interface for the DSA switch devices. The interface can be mounted with: # mount -t debugfs none /sys/kernel/debug The dsa directory contains one directory per switch chip: # cd

[PATCH net-next v2 08/10] net: dsa: debugfs: add port mdb

Add a debug filesystem "mdb" entry to query a port's hardware MDB entries through the .port_mdb_dump switch operation. This is really convenient to query directly the hardware or inspect DSA or CPU links, since these ports are not exposed to userspace. Signed-off-by: Vivien Didelot

Re: [PATCH 03/10] perf: Make sure we read only scheduled events

On Thu, Aug 24, 2017 at 06:27:30PM +0200, Jiri Olsa wrote: > Adding leader's state check into perf_output_read_group > to ensure we read only leader, which is scheduled in. > > Similar check is already there for siblings. > > Signed-off-by: Jiri Olsa > --- >

[PATCH net-next v2 08/10] net: dsa: debugfs: add port mdb

Add a debug filesystem "mdb" entry to query a port's hardware MDB entries through the .port_mdb_dump switch operation. This is really convenient to query directly the hardware or inspect DSA or CPU links, since these ports are not exposed to userspace. Signed-off-by: Vivien Didelot Reviewed-by:

Re: [PATCH 03/10] perf: Make sure we read only scheduled events

On Thu, Aug 24, 2017 at 06:27:30PM +0200, Jiri Olsa wrote: > Adding leader's state check into perf_output_read_group > to ensure we read only leader, which is scheduled in. > > Similar check is already there for siblings. > > Signed-off-by: Jiri Olsa > --- > kernel/events/core.c | 10

[PATCH net-next v2 10/10] net: dsa: debugfs: add port vlan

Add a debug filesystem "vlan" entry to query a port's hardware VLAN entries through the .port_vlan_dump switch operation. This is really convenient to query directly the hardware or inspect DSA or CPU links, since these ports are not exposed to userspace. Here are the VLAN entries for a CPU

[PATCH net-next v2 10/10] net: dsa: debugfs: add port vlan

Add a debug filesystem "vlan" entry to query a port's hardware VLAN entries through the .port_vlan_dump switch operation. This is really convenient to query directly the hardware or inspect DSA or CPU links, since these ports are not exposed to userspace. Here are the VLAN entries for a CPU

Re: [PATCH 02/10] perf: Fix leader for removed sibling event in perf_group_detach

On Thu, Aug 24, 2017 at 06:27:29PM +0200, Jiri Olsa wrote: > Mark reported warning in x86_perf_event_update caused > by reading unscheduled leader of an event that was > already removed from the group. > > As he pointed out we don't properly reset event's leader > once it's been detached from the

Re: [PATCH 02/10] perf: Fix leader for removed sibling event in perf_group_detach

On Thu, Aug 24, 2017 at 06:27:29PM +0200, Jiri Olsa wrote: > Mark reported warning in x86_perf_event_update caused > by reading unscheduled leader of an event that was > already removed from the group. > > As he pointed out we don't properly reset event's leader > once it's been detached from the

[PATCH net-next v2 02/10] net: dsa: debugfs: add tree

This commit adds the boiler plate to create a DSA related debug filesystem entry as well as a "tree" file, containing the tree index. # cat switch1/tree 0 Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli Reviewed-by:

[PATCH net-next v2 02/10] net: dsa: debugfs: add tree

This commit adds the boiler plate to create a DSA related debug filesystem entry as well as a "tree" file, containing the tree index. # cat switch1/tree 0 Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli Reviewed-by: Andrew Lunn --- net/dsa/debugfs.c | 107

[PATCH net-next v2 00/10] net: dsa: add generic debugfs interface

This patch series adds a generic debugfs interface for the DSA framework, so that all switch devices benefit from it, e.g. Marvell, Broadcom, Microchip or any other DSA driver. This is really convenient for debugging, especially CPU ports and DSA links which are not exposed to userspace as net

[PATCH net-next v2 00/10] net: dsa: add generic debugfs interface

This patch series adds a generic debugfs interface for the DSA framework, so that all switch devices benefit from it, e.g. Marvell, Broadcom, Microchip or any other DSA driver. This is really convenient for debugging, especially CPU ports and DSA links which are not exposed to userspace as net

[PATCH net-next v2 09/10] net: dsa: restore VLAN dump

This commit defines a dsa_vlan_dump_cb_t callback, similar to the FDB dump callback and partly reverts commit a0b6b8c9fa3c ("net: dsa: Remove support for vlan dump from DSA's drivers") to restore the DSA drivers VLAN dump operations. Signed-off-by: Vivien Didelot

[PATCH net-next v2 09/10] net: dsa: restore VLAN dump

This commit defines a dsa_vlan_dump_cb_t callback, similar to the FDB dump callback and partly reverts commit a0b6b8c9fa3c ("net: dsa: Remove support for vlan dump from DSA's drivers") to restore the DSA drivers VLAN dump operations. Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli

[PATCH net-next v2 03/10] net: dsa: debugfs: add tag_protocol

Add a debug filesystem "tag_protocol" entry to query the switch tagging protocol through the .get_tag_protocol operation. # cat switch1/tag_protocol EDSA To ease maintenance of tag protocols, add a dsa_tag_protocol_name helper to the public API which to convert a tag protocol enum to a

[PATCH net-next v2 03/10] net: dsa: debugfs: add tag_protocol

Add a debug filesystem "tag_protocol" entry to query the switch tagging protocol through the .get_tag_protocol operation. # cat switch1/tag_protocol EDSA To ease maintenance of tag protocols, add a dsa_tag_protocol_name helper to the public API which to convert a tag protocol enum to a

[PATCH net-next v2 04/10] net: dsa: debugfs: add port stats

Add a debug filesystem "stats" entry to query a port's hardware statistics through the DSA switch .get_sset_count, .get_strings and .get_ethtool_stats operations. This allows one to get statistics about DSA links interconnecting switches, which is very convenient because this kind of port is not

[PATCH net-next v2 05/10] net: dsa: debugfs: add port regs

Add a debug filesystem "regs" entry to query a port's hardware registers through the .get_regs_len and .get_regs_len switch operations. This is very convenient because it allows one to dump the registers of DSA links, which are not exposed to userspace. Here are the registers of a zii-rev-b CPU

[PATCH net-next v2 04/10] net: dsa: debugfs: add port stats

Add a debug filesystem "stats" entry to query a port's hardware statistics through the DSA switch .get_sset_count, .get_strings and .get_ethtool_stats operations. This allows one to get statistics about DSA links interconnecting switches, which is very convenient because this kind of port is not

[PATCH net-next v2 05/10] net: dsa: debugfs: add port regs

Add a debug filesystem "regs" entry to query a port's hardware registers through the .get_regs_len and .get_regs_len switch operations. This is very convenient because it allows one to dump the registers of DSA links, which are not exposed to userspace. Here are the registers of a zii-rev-b CPU

[PATCH net-next v2 06/10] net: dsa: debugfs: add port fdb

Add a debug filesystem "fdb" entry to query a port's hardware FDB entries through the .port_fdb_dump switch operation. This is really convenient to query directly the hardware or inspect DSA or CPU links, since these ports are not exposed to userspace. # cat port1/fdb vid 0

[PATCH net-next v2 06/10] net: dsa: debugfs: add port fdb

Add a debug filesystem "fdb" entry to query a port's hardware FDB entries through the .port_fdb_dump switch operation. This is really convenient to query directly the hardware or inspect DSA or CPU links, since these ports are not exposed to userspace. # cat port1/fdb vid 0

Re: [PATCH v2 4/5] cramfs: add mmap support

On Mon, 28 Aug 2017, Al Viro wrote: > On Mon, Aug 28, 2017 at 09:29:58AM -0400, Nicolas Pitre wrote: > > > > + /* Make sure the vma didn't change between the locks */ > > > > + vma = find_vma(mm, vmf->address); > > > > + if (vma->vm_ops != _vmasplit_ops) { > > > > +

Re: [PATCH v2 4/5] cramfs: add mmap support

On Mon, 28 Aug 2017, Al Viro wrote: > On Mon, Aug 28, 2017 at 09:29:58AM -0400, Nicolas Pitre wrote: > > > > + /* Make sure the vma didn't change between the locks */ > > > > + vma = find_vma(mm, vmf->address); > > > > + if (vma->vm_ops != _vmasplit_ops) { > > > > +

Re: [PATCH v8 2/3] PCI: iproc: retry request when CRS returned from EP

On Thu, Aug 24, 2017 at 10:34:25AM +0530, Oza Pawandeep wrote: > PCIe spec r3.1, sec 2.3.2 > If CRS software visibility is not enabled, the RC must reissue the > config request as a new request. > > - If CRS software visibility is enabled, > - for a config read of Vendor ID, the RC must return

Re: [PATCH v8 2/3] PCI: iproc: retry request when CRS returned from EP

On Thu, Aug 24, 2017 at 10:34:25AM +0530, Oza Pawandeep wrote: > PCIe spec r3.1, sec 2.3.2 > If CRS software visibility is not enabled, the RC must reissue the > config request as a new request. > > - If CRS software visibility is enabled, > - for a config read of Vendor ID, the RC must return

Re: [PATCH V3] acpi: apei: clear error status before acknowledging the error

On Mon, Aug 28, 2017 at 9:27 PM, Borislav Petkov wrote: > On Mon, Aug 28, 2017 at 08:44:21PM +0300, Andy Shevchenko wrote: >> For my opinion, since you asked, the either case needs a comment on >> top of that additional check. > > That's because the comment belongs to the v2 part of

Re: [PATCH V3] acpi: apei: clear error status before acknowledging the error

On Mon, Aug 28, 2017 at 9:27 PM, Borislav Petkov wrote: > On Mon, Aug 28, 2017 at 08:44:21PM +0300, Andy Shevchenko wrote: >> For my opinion, since you asked, the either case needs a comment on >> top of that additional check. > > That's because the comment belongs to the v2 part of the check.

Re: [PATCH V3] acpi: apei: clear error status before acknowledging the error

On Mon, Aug 28, 2017 at 9:27 PM, Borislav Petkov wrote: > On Mon, Aug 28, 2017 at 08:44:21PM +0300, Andy Shevchenko wrote: >> For my opinion, since you asked, the either case needs a comment on >> top of that additional check. > > That's because the comment belongs to the v2 part of

Re: [PATCH V3] acpi: apei: clear error status before acknowledging the error

On Mon, Aug 28, 2017 at 9:27 PM, Borislav Petkov wrote: > On Mon, Aug 28, 2017 at 08:44:21PM +0300, Andy Shevchenko wrote: >> For my opinion, since you asked, the either case needs a comment on >> top of that additional check. > > That's because the comment belongs to the v2 part of the check. >

Re: [PATCH v2 11/14] power: supply: bq24190_charger: Get input_current_limit from our supplier

Hi, On 28-08-17 20:07, Liam Breck wrote: Hi Hans, I sent too soon... On Mon, Aug 28, 2017 at 9:04 AM, Hans de Goede wrote: Hi, On 16-08-17 22:28, Liam Breck wrote: Hi Hans, On Tue, Aug 15, 2017 at 1:04 PM, Hans de Goede wrote: On some devices

Re: [PATCH v2 11/14] power: supply: bq24190_charger: Get input_current_limit from our supplier

Hi, On 28-08-17 20:07, Liam Breck wrote: Hi Hans, I sent too soon... On Mon, Aug 28, 2017 at 9:04 AM, Hans de Goede wrote: Hi, On 16-08-17 22:28, Liam Breck wrote: Hi Hans, On Tue, Aug 15, 2017 at 1:04 PM, Hans de Goede wrote: On some devices the USB Type-C port power (USB PD 2.0)

Re: [PATCH v3 0/5] fs/dcache: Limit # of negative dentries

On 08/28/2017 01:58 PM, Waiman Long wrote: > On 07/28/2017 02:34 PM, Waiman Long wrote: >> v2->v3: >> - Add a faster pruning rate when the free pool is closed to depletion. >> - As suggested by James Bottomley, add an artificial delay waiting >> loop before killing a negative dentry and

Re: [PATCH v3 0/5] fs/dcache: Limit # of negative dentries

On 08/28/2017 01:58 PM, Waiman Long wrote: > On 07/28/2017 02:34 PM, Waiman Long wrote: >> v2->v3: >> - Add a faster pruning rate when the free pool is closed to depletion. >> - As suggested by James Bottomley, add an artificial delay waiting >> loop before killing a negative dentry and

Re: [PATCH] hugetlbfs: change put_page/unlock_page order in hugetlbfs_fallocate()

On 08/28/2017 11:09 AM, Michal Hocko wrote: > On Mon 28-08-17 10:45:58, Mike Kravetz wrote: >> Adding Andrew, Michal on CC >> >> On 08/27/2017 01:08 PM, Nadav Amit wrote: >>> Mike Kravetz wrote: >>> On 08/26/2017 12:11 PM, Nadav Amit wrote: > hugetlfs_fallocate()

Re: [PATCH] hugetlbfs: change put_page/unlock_page order in hugetlbfs_fallocate()

On 08/28/2017 11:09 AM, Michal Hocko wrote: > On Mon 28-08-17 10:45:58, Mike Kravetz wrote: >> Adding Andrew, Michal on CC >> >> On 08/27/2017 01:08 PM, Nadav Amit wrote: >>> Mike Kravetz wrote: >>> On 08/26/2017 12:11 PM, Nadav Amit wrote: > hugetlfs_fallocate() currently performs

Re: linux-next: manual merge of the scsi tree with the staging tree

On Mon, Aug 28, 2017 at 06:51:59PM +0100, James Bottomley wrote: > On Mon, 2017-08-28 at 18:44 +0200, g...@kroah.com wrote: > > On Mon, Aug 28, 2017 at 04:36:06PM +, Bart Van Assche wrote: > > > > > > On Mon, 2017-08-28 at 18:05 +0200, g...@kroah.com wrote: > > > > > > > > On Mon, Aug 28,

Re: linux-next: manual merge of the scsi tree with the staging tree

On Mon, Aug 28, 2017 at 06:51:59PM +0100, James Bottomley wrote: > On Mon, 2017-08-28 at 18:44 +0200, g...@kroah.com wrote: > > On Mon, Aug 28, 2017 at 04:36:06PM +, Bart Van Assche wrote: > > > > > > On Mon, 2017-08-28 at 18:05 +0200, g...@kroah.com wrote: > > > > > > > > On Mon, Aug 28,

Re: [PATCH v2] [media] pci: make video_device const

On 26/Aug/2017 18:38, Bhumika Goyal wrote: > Make these const as they are either used during a copy operation or > passed to a const argument of the function cx88_vdev_init. > > Signed-off-by: Bhumika Goyal > --- > * Combine the patch series sent for drivers/media/pci/ into a

Re: [PATCH v2] [media] pci: make video_device const

On 26/Aug/2017 18:38, Bhumika Goyal wrote: > Make these const as they are either used during a copy operation or > passed to a const argument of the function cx88_vdev_init. > > Signed-off-by: Bhumika Goyal > --- > * Combine the patch series sent for drivers/media/pci/ into a > single patch. >

Re: [PATCH 3/5] [media] solo6x10: make video_device const

On 26/Aug/2017 16:43, Bhumika Goyal wrote: > Make this const as it is only used in a copy operation. > > Signed-off-by: Bhumika Goyal > --- > drivers/media/pci/solo6x10/solo6x10-v4l2.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH 3/5] [media] solo6x10: make video_device const

On 26/Aug/2017 16:43, Bhumika Goyal wrote: > Make this const as it is only used in a copy operation. > > Signed-off-by: Bhumika Goyal > --- > drivers/media/pci/solo6x10/solo6x10-v4l2.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

boot failure with 4.13.0-rc6 due to ATA errors

Not sure why mailing list to direct this bug report to, so starting with libata based on the error messages. Some where between v4.12 and 4.13.0-rc6 a Celestica redstone switch fails to boot due to ATA errors: [9.185203] ata1.00: failed to set xfermode (err_mask=0x40) [9.500825] ata1.00:

boot failure with 4.13.0-rc6 due to ATA errors

Not sure why mailing list to direct this bug report to, so starting with libata based on the error messages. Some where between v4.12 and 4.13.0-rc6 a Celestica redstone switch fails to boot due to ATA errors: [9.185203] ata1.00: failed to set xfermode (err_mask=0x40) [9.500825] ata1.00:

Re: [PATCH] packet: Don't write vnet header beyond end of buffer

On Mon, Aug 28, 2017 at 2:29 PM, Benjamin Poirier wrote: > ... which may happen with certain values of tp_reserve and maclen. > > Fixes: 58d19b19cd99 ("packet: vnet_hdr support for tpacket_rcv") > Signed-off-by: Benjamin Poirier > Cc: Willem de Bruijn

Re: [PATCH] packet: Don't write vnet header beyond end of buffer

On Mon, Aug 28, 2017 at 2:29 PM, Benjamin Poirier wrote: > ... which may happen with certain values of tp_reserve and maclen. > > Fixes: 58d19b19cd99 ("packet: vnet_hdr support for tpacket_rcv") > Signed-off-by: Benjamin Poirier > Cc: Willem de Bruijn Acked-by: Willem de Bruijn Thanks for

Re: [PATCH] IPMI: make ipmi_poweroff_handler const

On 08/28/2017 01:08 PM, Bhumika Goyal wrote: Make this const as it is only passed to a const argument of the function ipmi_create_user. Queued for the next kernel release. -corey Signed-off-by: Bhumika Goyal --- drivers/char/ipmi/ipmi_poweroff.c | 2 +- 1 file

Re: [PATCH] IPMI: make ipmi_poweroff_handler const

On 08/28/2017 01:08 PM, Bhumika Goyal wrote: Make this const as it is only passed to a const argument of the function ipmi_create_user. Queued for the next kernel release. -corey Signed-off-by: Bhumika Goyal --- drivers/char/ipmi/ipmi_poweroff.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH] tty: hvcs: make ktermios const

On 08/28/2017 11:30 AM, Bhumika Goyal wrote: > Make this const as it is not modified anywhere. > > Signed-off-by: Bhumika Goyal Reviewed-by: Tyrel Datwyler

Re: [PATCH] tty: hvcs: make ktermios const

On 08/28/2017 11:30 AM, Bhumika Goyal wrote: > Make this const as it is not modified anywhere. > > Signed-off-by: Bhumika Goyal Reviewed-by: Tyrel Datwyler

Re: [PATCH v3 56/59] KVM: arm/arm64: GICv4: Prevent heterogenous systems from using GICv4

On Mon, Jul 31, 2017 at 06:26:34PM +0100, Marc Zyngier wrote: > The GICv4 architecture doesn't prevent CPUs implementing GICv4 to > cohabit with CPUs limited to GICv3 in the same system. > > This is mad (the sheduler would have to be made aware of the v4 *scheduler > capability), and we're

Re: [PATCH v3 56/59] KVM: arm/arm64: GICv4: Prevent heterogenous systems from using GICv4

On Mon, Jul 31, 2017 at 06:26:34PM +0100, Marc Zyngier wrote: > The GICv4 architecture doesn't prevent CPUs implementing GICv4 to > cohabit with CPUs limited to GICv3 in the same system. > > This is mad (the sheduler would have to be made aware of the v4 *scheduler > capability), and we're

Re: [PATCH 4/7] ipv4: make net_protocol const

From: Bhumika Goyal Date: Fri, 25 Aug 2017 19:51:44 +0530 > Make these const as they are only passed to a const argument of the > function inet_add_protocol. > > Signed-off-by: Bhumika Goyal Applied.

Re: [PATCH 0/6] perf tools: Minor build fixes

On Mon, Aug 28, 2017 at 7:16 AM, Arnaldo Carvalho de Melo wrote: > Em Mon, Aug 28, 2017 at 11:34:21AM +0200, Jiri Olsa escreveu: >> On Sun, Aug 27, 2017 at 12:54:36AM -0700, David Carrillo-Cisneros wrote: >> > Collection of minor fixes to compile with LLVM and >> > non-standard

Re: [PATCH 4/7] ipv4: make net_protocol const

From: Bhumika Goyal Date: Fri, 25 Aug 2017 19:51:44 +0530 > Make these const as they are only passed to a const argument of the > function inet_add_protocol. > > Signed-off-by: Bhumika Goyal Applied.

Re: [PATCH 0/6] perf tools: Minor build fixes

On Mon, Aug 28, 2017 at 7:16 AM, Arnaldo Carvalho de Melo wrote: > Em Mon, Aug 28, 2017 at 11:34:21AM +0200, Jiri Olsa escreveu: >> On Sun, Aug 27, 2017 at 12:54:36AM -0700, David Carrillo-Cisneros wrote: >> > Collection of minor fixes to compile with LLVM and >> > non-standard tool names. >> >

Re: [PATCH 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

On Mon, 2017-08-28 at 14:22:03 -0400, Nicolas Dufresne wrote: > Le lundi 28 août 2017 à 08:15 -0700, Soren Brinkmann a écrit : [...] > > diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig > > index 94153895fcd4..4e8b64575b2a 100644 > > --- a/drivers/media/i2c/Kconfig > > +++

Re: [PATCH 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

On Mon, 2017-08-28 at 14:22:03 -0400, Nicolas Dufresne wrote: > Le lundi 28 août 2017 à 08:15 -0700, Soren Brinkmann a écrit : [...] > > diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig > > index 94153895fcd4..4e8b64575b2a 100644 > > --- a/drivers/media/i2c/Kconfig > > +++

Re: [PATCH 5/7] RDS: make rhashtable_params const

From: Bhumika Goyal Date: Fri, 25 Aug 2017 19:51:45 +0530 > Make this const as it is either used during a copy operation or passed > to a const argument of the function rhltable_init > > Signed-off-by: Bhumika Goyal Applied.

Re: [PATCH 5/7] RDS: make rhashtable_params const

From: Bhumika Goyal Date: Fri, 25 Aug 2017 19:51:45 +0530 > Make this const as it is either used during a copy operation or passed > to a const argument of the function rhltable_init > > Signed-off-by: Bhumika Goyal Applied.

[PATCH] perf tools: Remove BUG_ON char[] to bool implicit conversions

When compiling with LLVM, errors like this are shown: builtin-lock.c:46:10: error: implicit conversion turns string literal into bool: 'const char [39]' to 'bool' due to error message implicit conversion into bool. Fix it printing the error message and returning an error when possible.

[PATCH] perf tools: Remove BUG_ON char[] to bool implicit conversions

When compiling with LLVM, errors like this are shown: builtin-lock.c:46:10: error: implicit conversion turns string literal into bool: 'const char [39]' to 'bool' due to error message implicit conversion into bool. Fix it printing the error message and returning an error when possible.

[PATCH] tty: hvcs: make ktermios const

Make this const as it is not modified anywhere. Signed-off-by: Bhumika Goyal --- drivers/tty/hvc/hvcs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/hvc/hvcs.c b/drivers/tty/hvc/hvcs.c index 79cc5be..40adf86 100644 ---

[PATCH] tty: hvcs: make ktermios const

Make this const as it is not modified anywhere. Signed-off-by: Bhumika Goyal --- drivers/tty/hvc/hvcs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/hvc/hvcs.c b/drivers/tty/hvc/hvcs.c index 79cc5be..40adf86 100644 --- a/drivers/tty/hvc/hvcs.c +++

[PATCH] packet: Don't write vnet header beyond end of buffer

... which may happen with certain values of tp_reserve and maclen. Fixes: 58d19b19cd99 ("packet: vnet_hdr support for tpacket_rcv") Signed-off-by: Benjamin Poirier Cc: Willem de Bruijn --- net/packet/af_packet.c | 12 +--- 1 file changed, 9

[PATCH] packet: Don't write vnet header beyond end of buffer

... which may happen with certain values of tp_reserve and maclen. Fixes: 58d19b19cd99 ("packet: vnet_hdr support for tpacket_rcv") Signed-off-by: Benjamin Poirier Cc: Willem de Bruijn --- net/packet/af_packet.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 2/7] bridge: make ebt_table const

From: Bhumika Goyal Date: Fri, 25 Aug 2017 19:51:42 +0530 > Make this const as it is only passed to a const argument of the function > ebt_register_table. > > Signed-off-by: Bhumika Goyal Applied.

Re: [PATCH 2/7] bridge: make ebt_table const

From: Bhumika Goyal Date: Fri, 25 Aug 2017 19:51:42 +0530 > Make this const as it is only passed to a const argument of the function > ebt_register_table. > > Signed-off-by: Bhumika Goyal Applied.

[PATCH] sparc64: vcc: make ktermios const

Make this const as it is not modified anywhere. Signed-off-by: Bhumika Goyal --- drivers/tty/vcc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/vcc.c b/drivers/tty/vcc.c index 5e60817..f7e07e1 100644 --- a/drivers/tty/vcc.c +++

[PATCH] sparc64: vcc: make ktermios const

Make this const as it is not modified anywhere. Signed-off-by: Bhumika Goyal --- drivers/tty/vcc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/vcc.c b/drivers/tty/vcc.c index 5e60817..f7e07e1 100644 --- a/drivers/tty/vcc.c +++ b/drivers/tty/vcc.c @@ -102,7

Re: [PATCH V3] acpi: apei: clear error status before acknowledging the error

On Mon, Aug 28, 2017 at 08:44:21PM +0300, Andy Shevchenko wrote: > For my opinion, since you asked, the either case needs a comment on > top of that additional check. That's because the comment belongs to the v2 part of the check. > Separate conditionals in independent cases are, of course,

Re: [PATCH V3] acpi: apei: clear error status before acknowledging the error

On Mon, Aug 28, 2017 at 08:44:21PM +0300, Andy Shevchenko wrote: > For my opinion, since you asked, the either case needs a comment on > top of that additional check. That's because the comment belongs to the v2 part of the check. > Separate conditionals in independent cases are, of course,

Re: [PATCH net v2 1/4] net: mvpp2: fix the mac address used when using PPv2.2

From: Antoine Tenart Date: Fri, 25 Aug 2017 16:14:17 +0200 > The mac address is only retrieved from h/w when using PPv2.1. Otherwise > the variable holding it is still checked and used if it contains a valid > value. As the variable isn't initialized to an

Re: [PATCH net v2 1/4] net: mvpp2: fix the mac address used when using PPv2.2

From: Antoine Tenart Date: Fri, 25 Aug 2017 16:14:17 +0200 > The mac address is only retrieved from h/w when using PPv2.1. Otherwise > the variable holding it is still checked and used if it contains a valid > value. As the variable isn't initialized to an invalid mac address > value, we end up

Re: [PATCH v3 55/59] KVM: arm/arm64: GICv4: Enable VLPI support

On Mon, Jul 31, 2017 at 06:26:33PM +0100, Marc Zyngier wrote: > All it takes is the has_v4 flag to be set in gic_kvm_info > as well as "kvm-arm.vgic_v4_enable=1" being passed on the > command line for GICv4 to be enabled in KVM. > > Signed-off-by: Marc Zyngier So I'm

Re: [PATCH v3 55/59] KVM: arm/arm64: GICv4: Enable VLPI support

On Mon, Jul 31, 2017 at 06:26:33PM +0100, Marc Zyngier wrote: > All it takes is the has_v4 flag to be set in gic_kvm_info > as well as "kvm-arm.vgic_v4_enable=1" being passed on the > command line for GICv4 to be enabled in KVM. > > Signed-off-by: Marc Zyngier So I'm wondering if we should have

Re: [PATCH v2] cdc_ncm: flag the u-blox TOBY-L4 as wwan

From: Aleksander Morgado Date: Fri, 25 Aug 2017 15:39:16 +0200 > The u-blox TOBY-L4 is a LTE Advanced (Cat 6) module with HSPA+ and 2G > fallback. > > Unlike the TOBY-L2, this module has one single USB layout and exposes > several TTYs for control and a NCM interface

Re: [PATCH v2] cdc_ncm: flag the u-blox TOBY-L4 as wwan

From: Aleksander Morgado Date: Fri, 25 Aug 2017 15:39:16 +0200 > The u-blox TOBY-L4 is a LTE Advanced (Cat 6) module with HSPA+ and 2G > fallback. > > Unlike the TOBY-L2, this module has one single USB layout and exposes > several TTYs for control and a NCM interface for data. Connecting this >

Re: [PATCH][pci-next] PCI: endpoint: fix incorrect end of table check in while loop

On Wed, Aug 23, 2017 at 05:03:03PM +0100, Colin King wrote: > From: Colin Ian King > > Currently, the while loop will iterate until a matching name is found > or until the id pointer wraps around to NULL (the latter is incorrect). > > The end of a pci_epf_device_id

Re: [PATCH][pci-next] PCI: endpoint: fix incorrect end of table check in while loop

On Wed, Aug 23, 2017 at 05:03:03PM +0100, Colin King wrote: > From: Colin Ian King > > Currently, the while loop will iterate until a matching name is found > or until the id pointer wraps around to NULL (the latter is incorrect). > > The end of a pci_epf_device_id table is terminated with

Re: [RFCv4 1/6] sched/core: add utilization clamping to CPU controller

Hello, No idea whether this makes sense overall. I'll just comment on the cgroup interface part. On Thu, Aug 24, 2017 at 07:08:52PM +0100, Patrick Bellasi wrote: > This patch extends the CPU controller by adding a couple of new attributes, > util_min and util_max, which can be used to enforce

Re: [RFCv4 1/6] sched/core: add utilization clamping to CPU controller

Hello, No idea whether this makes sense overall. I'll just comment on the cgroup interface part. On Thu, Aug 24, 2017 at 07:08:52PM +0100, Patrick Bellasi wrote: > This patch extends the CPU controller by adding a couple of new attributes, > util_min and util_max, which can be used to enforce

Re: I/O hangs after resuming from suspend-to-ram

Hi. On pondělí 28. srpna 2017 14:58:28 CEST Ming Lei wrote: > Could you verify if the following patch fixes your issue? > …SNIP… I've applied it to v4.12.9 and rechecked — the issue is still there, unfortunately. Stacktrace is the same as before. Were you able to reproduce it in a VM? Should

Re: I/O hangs after resuming from suspend-to-ram

Hi. On pondělí 28. srpna 2017 14:58:28 CEST Ming Lei wrote: > Could you verify if the following patch fixes your issue? > …SNIP… I've applied it to v4.12.9 and rechecked — the issue is still there, unfortunately. Stacktrace is the same as before. Were you able to reproduce it in a VM? Should

Re: [PATCH v3 42/59] KVM: arm/arm64: GICv4: Handle INT command applied to a VLPI

On Mon, Jul 31, 2017 at 06:26:20PM +0100, Marc Zyngier wrote: > If the guest issues an INT command targetting a VLPI, let's > call into the irq_set_irqchip_state() helper to make it pending > on the physical side. > > This works just as well if userspace decides to inject an interrupt > using the

Re: [PATCH 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

Le lundi 28 août 2017 à 08:15 -0700, Soren Brinkmann a écrit : > From: Leon Luo > > The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. > It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface > is 4-lane MIPI running at 1.44Gbps each. > >

Re: [PATCH v3 42/59] KVM: arm/arm64: GICv4: Handle INT command applied to a VLPI

On Mon, Jul 31, 2017 at 06:26:20PM +0100, Marc Zyngier wrote: > If the guest issues an INT command targetting a VLPI, let's > call into the irq_set_irqchip_state() helper to make it pending > on the physical side. > > This works just as well if userspace decides to inject an interrupt > using the

Re: [PATCH 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

Le lundi 28 août 2017 à 08:15 -0700, Soren Brinkmann a écrit : > From: Leon Luo > > The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. > It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface > is 4-lane MIPI running at 1.44Gbps each. > > This driver has been tested

Re: [PATCH v3 45/59] KVM: arm/arm64: GICv4: Handle CLEAR applied to a VLPI

On Mon, Jul 31, 2017 at 06:26:23PM +0100, Marc Zyngier wrote: > Handling CLEAR is pretty easy. Just ask the ITS driver to clear > the corresponding pending bit (which will turn into a CLEAR > command on the physical side). > > Signed-off-by: Marc Zyngier Acked-by:

Re: [PATCH v3 45/59] KVM: arm/arm64: GICv4: Handle CLEAR applied to a VLPI

On Mon, Jul 31, 2017 at 06:26:23PM +0100, Marc Zyngier wrote: > Handling CLEAR is pretty easy. Just ask the ITS driver to clear > the corresponding pending bit (which will turn into a CLEAR > command on the physical side). > > Signed-off-by: Marc Zyngier Acked-by: Christoffer Dall > --- >

Re: [PATCH v3 54/59] KVM: arm/arm64: GICv4: Enable virtual cpuif if VLPIs can be delivered

On Mon, Jul 31, 2017 at 06:26:32PM +0100, Marc Zyngier wrote: > In order for VLPIs to be delivered to the guest, we must make > sure that the cpuif is always enabled, irrespective of the > presence of virtual interrupt in the LRs. > > Signed-off-by: Marc Zyngier > --- >

Re: [PATCH v3 54/59] KVM: arm/arm64: GICv4: Enable virtual cpuif if VLPIs can be delivered

On Mon, Jul 31, 2017 at 06:26:32PM +0100, Marc Zyngier wrote: > In order for VLPIs to be delivered to the guest, we must make > sure that the cpuif is always enabled, irrespective of the > presence of virtual interrupt in the LRs. > > Signed-off-by: Marc Zyngier > --- >

Re: [PATCH] nokia n900: update dts with camera support

Hi On 28.08.2017 18:07, Sakari Ailus wrote: Hi Pavel, On Mon, Aug 28, 2017 at 03:59:59PM +0200, Pavel Machek wrote: Hi! Well, strobe property above already uses = <0>/<1> format, as do others. Problem with "false = property does not exist" is that you don't know if it is "someone forgot

Re: [PATCH] nokia n900: update dts with camera support

Hi On 28.08.2017 18:07, Sakari Ailus wrote: Hi Pavel, On Mon, Aug 28, 2017 at 03:59:59PM +0200, Pavel Machek wrote: Hi! Well, strobe property above already uses = <0>/<1> format, as do others. Problem with "false = property does not exist" is that you don't know if it is "someone forgot

Re: [PATCH v3 47/59] KVM: arm/arm64: GICv4: Propagate property updates to VLPIs

On Mon, Jul 31, 2017 at 06:26:25PM +0100, Marc Zyngier wrote: > Upon updating a property, we propagate it all the way to the physical > ITS, and ask for an INV command to be executed there. > > Signed-off-by: Marc Zyngier Acked-by: Christoffer Dall >

Re: [PATCH v3 47/59] KVM: arm/arm64: GICv4: Propagate property updates to VLPIs

On Mon, Jul 31, 2017 at 06:26:25PM +0100, Marc Zyngier wrote: > Upon updating a property, we propagate it all the way to the physical > ITS, and ask for an INV command to be executed there. > > Signed-off-by: Marc Zyngier Acked-by: Christoffer Dall > --- > virt/kvm/arm/vgic/vgic-its.c | 3

Re: [PATCH v3 49/59] KVM: arm/arm64: GICv4: Propagate VLPI properties at map time

On Mon, Jul 31, 2017 at 06:26:27PM +0100, Marc Zyngier wrote: > When the VLPI gets mapped, it must inherit the configuration of > LPI configured at the vITS level. FOr that purpose, let's make *the LPI *For that > update_lpi_config globally available and call it just after > having performed the

Re: [PATCH v3 49/59] KVM: arm/arm64: GICv4: Propagate VLPI properties at map time

On Mon, Jul 31, 2017 at 06:26:27PM +0100, Marc Zyngier wrote: > When the VLPI gets mapped, it must inherit the configuration of > LPI configured at the vITS level. FOr that purpose, let's make *the LPI *For that > update_lpi_config globally available and call it just after > having performed the

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