Re: [PATCH net-next 06/12] net: bcmgenet: remove handling of wol interrupts from isr0

On 03/13/2017 05:41 PM, Doug Berger wrote: > The bcmgenet_wol_isr() handler performs the necessary processing for > waking from a GENET event. There is no necessary functionality behind > servicing the UMAC_IRQ_MPD_R event in the handling of isr0. Therefore > the code that unmasks and masks this

Re: arch/x86/include/asm/pgtable.h:888:2: error: implicit declaration of function 'native_pud_clear'

Hi Dave, On Mon, Mar 13, 2017 at 08:57:54AM -0700, Dave Jiang wrote: Fengguang, I don't believe Andrew has picked up this patch yet: http://marc.info/?l=linux-mm=148883870428812=2 Unless you are seeing issues with that patch. It looks the patch is not in mainline or linux-next yet: % git

Re: [PATCH net-next 05/12] net: bcmgenet: manage dma interrupts in napi code

On 03/13/2017 05:41 PM, Doug Berger wrote: > This commit moves DMA interrupt enabling out of init_umac() and adds > the masking of these interrupts to the napi enable and disable code. > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli --

Re: [PATCH net-next 05/12] net: bcmgenet: manage dma interrupts in napi code

On 03/13/2017 05:41 PM, Doug Berger wrote: > This commit moves DMA interrupt enabling out of init_umac() and adds > the masking of these interrupts to the napi enable and disable code. > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 04/12] net: bcmgenet: remove meaningless lines

On 03/13/2017 05:41 PM, Doug Berger wrote: > An assortment of non-functional lines are removed to reduce confusion > and some typos in comments are corrected. > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 04/12] net: bcmgenet: remove meaningless lines

On 03/13/2017 05:41 PM, Doug Berger wrote: > An assortment of non-functional lines are removed to reduce confusion > and some typos in comments are corrected. > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 03/12] net: bcmgenet: simplify circular pointer arithmetic

On 03/13/2017 05:41 PM, Doug Berger wrote: > A 2's complement subtraction will always do a borrow, so masking > off the sign bits is the same as conditionally adding (mask+1). > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 03/12] net: bcmgenet: simplify circular pointer arithmetic

On 03/13/2017 05:41 PM, Doug Berger wrote: > A 2's complement subtraction will always do a borrow, so masking > off the sign bits is the same as conditionally adding (mask+1). > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

[PATCH] genirq: Fix handle_nested_irq() for IRQF_SHARED

Shared interrupts can be registered with handle_nested_irq(), but currently only one of the registered handlers gets called. The use of shared interrupts with handle_nested_irq() is probably rare, but at least a case of a shared VBUS interrupt between USB PHY and battery charger drivers for a

[PATCH] genirq: Fix handle_nested_irq() for IRQF_SHARED

Shared interrupts can be registered with handle_nested_irq(), but currently only one of the registered handlers gets called. The use of shared interrupts with handle_nested_irq() is probably rare, but at least a case of a shared VBUS interrupt between USB PHY and battery charger drivers for a

Re: [PATCH net-next 02/12] net: phy: bcm7xxx: add support for 28nm EPHY

On 03/13/2017 05:41 PM, Doug Berger wrote: > This commit adds support for the internal fast ethernet 10/100 PHY > found in the BCM7260, BCM7268, and BCM7271 devices. > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 02/12] net: phy: bcm7xxx: add support for 28nm EPHY

On 03/13/2017 05:41 PM, Doug Berger wrote: > This commit adds support for the internal fast ethernet 10/100 PHY > found in the BCM7260, BCM7268, and BCM7271 devices. > > Signed-off-by: Doug Berger Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 01/12] net: phy: bcm-phylib: replace obsolete EEE macro references

On 03/13/2017 05:41 PM, Doug Berger wrote: > The macros MDIO_AN_EEE_ADV_100TX and MDIO_AN_EEE_ADV_1000T are now > considered obsolete and are replaced in the kernel with the generic > macros MDIO_EEE_100TX and MDIO_EEE_1000T respectively. > > Signed-off-by: Doug Berger

Re: [PATCH net-next 01/12] net: phy: bcm-phylib: replace obsolete EEE macro references

On 03/13/2017 05:41 PM, Doug Berger wrote: > The macros MDIO_AN_EEE_ADV_100TX and MDIO_AN_EEE_ADV_1000T are now > considered obsolete and are replaced in the kernel with the generic > macros MDIO_EEE_100TX and MDIO_EEE_1000T respectively. > > Signed-off-by: Doug Berger Reviewed-by: Florian

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hello, Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote: > On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > > This patchset introduces a TTY-based way for the synths to communicate > > with devices as an alternate for direct serial comms used by the synths > > at the

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hello, Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote: > On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > > This patchset introduces a TTY-based way for the synths to communicate > > with devices as an alternate for direct serial comms used by the synths > > at the

[PATCH net-next 02/12] net: phy: bcm7xxx: add support for 28nm EPHY

This commit adds support for the internal fast ethernet 10/100 PHY found in the BCM7260, BCM7268, and BCM7271 devices. Signed-off-by: Doug Berger --- drivers/net/phy/bcm7xxx.c | 215 +- include/linux/brcmphy.h | 3 + 2 files

[PATCH net-next 02/12] net: phy: bcm7xxx: add support for 28nm EPHY

This commit adds support for the internal fast ethernet 10/100 PHY found in the BCM7260, BCM7268, and BCM7271 devices. Signed-off-by: Doug Berger --- drivers/net/phy/bcm7xxx.c | 215 +- include/linux/brcmphy.h | 3 + 2 files changed, 216

[PATCH net-next 06/12] net: bcmgenet: remove handling of wol interrupts from isr0

The bcmgenet_wol_isr() handler performs the necessary processing for waking from a GENET event. There is no necessary functionality behind servicing the UMAC_IRQ_MPD_R event in the handling of isr0. Therefore the code that unmasks and masks this interrupt and that gets invoked in response to it

[PATCH net-next 06/12] net: bcmgenet: remove handling of wol interrupts from isr0

The bcmgenet_wol_isr() handler performs the necessary processing for waking from a GENET event. There is no necessary functionality behind servicing the UMAC_IRQ_MPD_R event in the handling of isr0. Therefore the code that unmasks and masks this interrupt and that gets invoked in response to it

[PATCH net-next 04/12] net: bcmgenet: remove meaningless lines

An assortment of non-functional lines are removed to reduce confusion and some typos in comments are corrected. Signed-off-by: Doug Berger --- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git

[PATCH net-next 04/12] net: bcmgenet: remove meaningless lines

An assortment of non-functional lines are removed to reduce confusion and some typos in comments are corrected. Signed-off-by: Doug Berger --- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git

[PATCH net-next 11/12] dt-bindings: net: update bcmgenet binding for GENETv5

The device tree documentation must be updated to reflect the new compatible strings "brcm,genet-v5" and "brcm,genet-mdio-v5" used by the GENETv5 driver. Signed-off-by: Doug Berger --- Documentation/devicetree/bindings/net/brcm,bcmgenet.txt| 10 +-

[PATCH net-next 11/12] dt-bindings: net: update bcmgenet binding for GENETv5

The device tree documentation must be updated to reflect the new compatible strings "brcm,genet-v5" and "brcm,genet-mdio-v5" used by the GENETv5 driver. Signed-off-by: Doug Berger --- Documentation/devicetree/bindings/net/brcm,bcmgenet.txt| 10 +-

[PATCH net-next 07/12] net: bcmgenet: clear status to reduce spurious interrupts

Since the DMA interrupt status is latched and the DMA servicing can be polled, it is a good idea to clear the latched status of a DMA interrupt before performing the service that would be invoked by the interrupt. This prevents old status from causing spurious interrupts when the interrupt is

[PATCH net-next 10/12] dt-bindings: net: document bcmgenet WoL interrupt

A third interrupt cell can be provided to optionally specify the interrupt used for handling Wake on LAN events. Typically the wake up handling uses a separate interrupt controller, so the interrupts-extended property is used to accommodate this. Signed-off-by: Doug Berger

[PATCH net-next 10/12] dt-bindings: net: document bcmgenet WoL interrupt

A third interrupt cell can be provided to optionally specify the interrupt used for handling Wake on LAN events. Typically the wake up handling uses a separate interrupt controller, so the interrupts-extended property is used to accommodate this. Signed-off-by: Doug Berger ---

[PATCH net-next 07/12] net: bcmgenet: clear status to reduce spurious interrupts

Since the DMA interrupt status is latched and the DMA servicing can be polled, it is a good idea to clear the latched status of a DMA interrupt before performing the service that would be invoked by the interrupt. This prevents old status from causing spurious interrupts when the interrupt is

[PATCH net-next 12/12] net: bcmgenet: add support for the GENETv5 hardware

This commit adds support for the GENETv5 implementation. The GENETv5 reports a major version of 6 instead of 5 so compensate for this when verifying the configuration of the driver. Also the EPHY revision is now contained in the MDIO registers of the PHY so the EPHY revision of 0 in

[PATCH net-next 12/12] net: bcmgenet: add support for the GENETv5 hardware

This commit adds support for the GENETv5 implementation. The GENETv5 reports a major version of 6 instead of 5 so compensate for this when verifying the configuration of the driver. Also the EPHY revision is now contained in the MDIO registers of the PHY so the EPHY revision of 0 in

[PATCH net-next 08/12] net: bcmgenet: correct return value of __bcmgenet_tx_reclaim

The reclaim function should return the number of buffer descriptors reclaimed, not just the number corresponding to skb packets. Also, remove the unnecessary computation when updating the consumer index. While this is not a functional problem it could degrade performance of napi in a fragmented

[PATCH net-next 05/12] net: bcmgenet: manage dma interrupts in napi code

This commit moves DMA interrupt enabling out of init_umac() and adds the masking of these interrupts to the napi enable and disable code. Signed-off-by: Doug Berger --- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 39 +++--- 1 file changed, 22

[PATCH net-next 08/12] net: bcmgenet: correct return value of __bcmgenet_tx_reclaim

The reclaim function should return the number of buffer descriptors reclaimed, not just the number corresponding to skb packets. Also, remove the unnecessary computation when updating the consumer index. While this is not a functional problem it could degrade performance of napi in a fragmented

[PATCH net-next 05/12] net: bcmgenet: manage dma interrupts in napi code

This commit moves DMA interrupt enabling out of init_umac() and adds the masking of these interrupts to the napi enable and disable code. Signed-off-by: Doug Berger --- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 39 +++--- 1 file changed, 22 insertions(+), 17

[PATCH net-next 09/12] net: bcmgenet: return EOPNOTSUPP for unknown ioctl commands

This commit changes the ioctl handling behavior to return the EOPNOTSUPP error code instead of the EINVAL error code when an unknown ioctl command value is detected. It also removes some redundant parsing of the ioctl command value and allows the SIOCSHWTSTAMP value to be handled. Signed-off-by:

[PATCH net-next 09/12] net: bcmgenet: return EOPNOTSUPP for unknown ioctl commands

This commit changes the ioctl handling behavior to return the EOPNOTSUPP error code instead of the EINVAL error code when an unknown ioctl command value is detected. It also removes some redundant parsing of the ioctl command value and allows the SIOCSHWTSTAMP value to be handled. Signed-off-by:

[PATCH net-next 00/12] net: bcmgenet: add support for GENETv5

This collection of patches contains changes related to adding support for the BCM7260, BCM7268, and BCM7271 devices that contain a new version of the GENET MAC IP block (v5) and a new fast ethernet (10/100BASE-T) internal PHY. These patches were originally developed on top of the bug fixes of the

[PATCH net-next 00/12] net: bcmgenet: add support for GENETv5

This collection of patches contains changes related to adding support for the BCM7260, BCM7268, and BCM7271 devices that contain a new version of the GENET MAC IP block (v5) and a new fast ethernet (10/100BASE-T) internal PHY. These patches were originally developed on top of the bug fixes of the

[PATCH net-next 03/12] net: bcmgenet: simplify circular pointer arithmetic

A 2's complement subtraction will always do a borrow, so masking off the sign bits is the same as conditionally adding (mask+1). Signed-off-by: Doug Berger --- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 19 +-- 1 file changed, 5 insertions(+), 14

[PATCH net-next 01/12] net: phy: bcm-phylib: replace obsolete EEE macro references

The macros MDIO_AN_EEE_ADV_100TX and MDIO_AN_EEE_ADV_1000T are now considered obsolete and are replaced in the kernel with the generic macros MDIO_EEE_100TX and MDIO_EEE_1000T respectively. Signed-off-by: Doug Berger --- drivers/net/phy/bcm-phy-lib.c | 6 +++--- 1 file

[PATCH net-next 03/12] net: bcmgenet: simplify circular pointer arithmetic

A 2's complement subtraction will always do a borrow, so masking off the sign bits is the same as conditionally adding (mask+1). Signed-off-by: Doug Berger --- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 19 +-- 1 file changed, 5 insertions(+), 14 deletions(-) diff --git

[PATCH net-next 01/12] net: phy: bcm-phylib: replace obsolete EEE macro references

The macros MDIO_AN_EEE_ADV_100TX and MDIO_AN_EEE_ADV_1000T are now considered obsolete and are replaced in the kernel with the generic macros MDIO_EEE_100TX and MDIO_EEE_1000T respectively. Signed-off-by: Doug Berger --- drivers/net/phy/bcm-phy-lib.c | 6 +++--- 1 file changed, 3 insertions(+),

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hello Okash, I'd say for a start already, rebase and submit patches 2-5, since they are refactoring that makes sense anyway. And we can discuss about serdev while that gets integrated, and thus serdev-equivalents of patches 1 and 6 will then be immediatetly applicable. Samuel

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Hello Okash, I'd say for a start already, rebase and submit patches 2-5, since they are refactoring that makes sense anyway. And we can discuss about serdev while that gets integrated, and thus serdev-equivalents of patches 1 and 6 will then be immediatetly applicable. Samuel

Re: [scsi] scsi: ufs: don't check unsigned type for a negative value

On 2017-03-12 03:22, Tomas Winkler wrote: Fix compilation warning drivers/scsi/ufs/ufshcd.c:7645:13: warning: comparison of unsigned expression < 0 is always false [-Wtype-limits] if ((value < UFS_PM_LVL_0) || (value >= UFS_PM_LVL_MAX)) Signed-off-by: Tomas Winkler

Re: [scsi] scsi: ufs: don't check unsigned type for a negative value

On 2017-03-12 03:22, Tomas Winkler wrote: Fix compilation warning drivers/scsi/ufs/ufshcd.c:7645:13: warning: comparison of unsigned expression < 0 is always false [-Wtype-limits] if ((value < UFS_PM_LVL_0) || (value >= UFS_PM_LVL_MAX)) Signed-off-by: Tomas Winkler ---

Re: [PATCH] staging: rtl8188eu: removed blank lines coding style problem

On Mon, Mar 13, 2017 at 09:00:49AM +0200, Andrii wrote: > Fix 'multiple blank lines' coding style problem reported by > checkpatch.pl. > > Signed-off-by: Andrii Vladyka Your From: name didn't match up with your signed-off-by: name here :( Please fix up and resend. thanks, greg

Re: [PATCH] staging: rtl8188eu: removed blank lines coding style problem

On Mon, Mar 13, 2017 at 09:00:49AM +0200, Andrii wrote: > Fix 'multiple blank lines' coding style problem reported by > checkpatch.pl. > > Signed-off-by: Andrii Vladyka Your From: name didn't match up with your signed-off-by: name here :( Please fix up and resend. thanks, greg k-h

Re: [PATCH 1/2] staging: wlan-ng: introduce a macro read_u16

On Mon, Mar 13, 2017 at 02:14:25PM +0100, Gioh Kim wrote: > read_u16 is wrapper of le16_to_cpu to read u16 variable, > rather than __le16. > > Signed-off-by: Gioh Kim > --- > drivers/staging/wlan-ng/prism2mgmt.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff

Re: [PATCH 1/2] staging: wlan-ng: introduce a macro read_u16

On Mon, Mar 13, 2017 at 02:14:25PM +0100, Gioh Kim wrote: > read_u16 is wrapper of le16_to_cpu to read u16 variable, > rather than __le16. > > Signed-off-by: Gioh Kim > --- > drivers/staging/wlan-ng/prism2mgmt.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git

Re: [PATCH] staging: rtl8192u: use __le16_to_cpu instead of cast

On Sun, Mar 12, 2017 at 04:02:35PM -0600, Perry Hooker wrote: > This patch fixes the following sparse warnings: > drivers/staging/rtl8192u/r8192U_dm.c:2307:49: warning: cast from restricted > __le16 > drivers/staging/rtl8192u/r8192U_dm.c:2308:44: warning: cast from restricted > __le16 >

Re: [PATCH] staging: rtl8192u: use __le16_to_cpu instead of cast

On Sun, Mar 12, 2017 at 04:02:35PM -0600, Perry Hooker wrote: > This patch fixes the following sparse warnings: > drivers/staging/rtl8192u/r8192U_dm.c:2307:49: warning: cast from restricted > __le16 > drivers/staging/rtl8192u/r8192U_dm.c:2308:44: warning: cast from restricted > __le16 >

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Samuel Thibault, on lun. 13 mars 2017 23:26:08 +0100, wrote: > > That should make this a lot easier than your patchset from what I can > > see. > > Will serdev support modem line control? We need this for some devices. "serdev: add serdev_device_set_rts" seems to be saying yes :) Samuel

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Samuel Thibault, on lun. 13 mars 2017 23:26:08 +0100, wrote: > > That should make this a lot easier than your patchset from what I can > > see. > > Will serdev support modem line control? We need this for some devices. "serdev: add serdev_device_set_rts" seems to be saying yes :) Samuel

Re: [PATCH 3/7] ath9k: Add support for reading the EEPROM data using the nvmem API

On Monday, March 13, 2017 10:05:11 PM CET Alban wrote: > Currently SoC platforms use a firmware request to get the EEPROM data. > This is mostly a hack and rely on using a user-helper scripts which is > deprecated. A nicer alternative is to use the nvmem API which was > designed for this kind of

Re: [PATCH 3/7] ath9k: Add support for reading the EEPROM data using the nvmem API

On Monday, March 13, 2017 10:05:11 PM CET Alban wrote: > Currently SoC platforms use a firmware request to get the EEPROM data. > This is mostly a hack and rely on using a user-helper scripts which is > deprecated. A nicer alternative is to use the nvmem API which was > designed for this kind of

[PATCH v3 6/7] xen/9pfs: receive responses

Upon receiving a notification from the backend, schedule the p9_xen_response work_struct. p9_xen_response checks if any responses are available, if so, it reads them one by one, calling p9_client_cb to send them up to the 9p layer (p9_client_cb completes the request). Handle the ring following the

[PATCH v3 6/7] xen/9pfs: receive responses

Upon receiving a notification from the backend, schedule the p9_xen_response work_struct. p9_xen_response checks if any responses are available, if so, it reads them one by one, calling p9_client_cb to send them up to the 9p layer (p9_client_cb completes the request). Handle the ring following the

[PATCH v3 5/7] xen/9pfs: send requests to the backend

Implement struct p9_trans_module create and close functions by looking at the available Xen 9pfs frontend-backend connections. We don't expect many frontend-backend connections, thus walking a list is OK. Send requests to the backend by copying each request to one of the available rings (each

[PATCH v3 7/7] xen/9pfs: build 9pfs Xen transport driver

This patch adds a Kconfig option and Makefile support for building the 9pfs Xen driver. Signed-off-by: Stefano Stabellini CC: boris.ostrov...@oracle.com CC: jgr...@suse.com CC: Eric Van Hensbergen CC: Ron Minnich CC: Latchesar Ionkov

[PATCH v3 5/7] xen/9pfs: send requests to the backend

Implement struct p9_trans_module create and close functions by looking at the available Xen 9pfs frontend-backend connections. We don't expect many frontend-backend connections, thus walking a list is OK. Send requests to the backend by copying each request to one of the available rings (each

[PATCH v3 7/7] xen/9pfs: build 9pfs Xen transport driver

This patch adds a Kconfig option and Makefile support for building the 9pfs Xen driver. Signed-off-by: Stefano Stabellini CC: boris.ostrov...@oracle.com CC: jgr...@suse.com CC: Eric Van Hensbergen CC: Ron Minnich CC: Latchesar Ionkov CC: v9fs-develo...@lists.sourceforge.net ---

[PATCH v3 4/7] xen/9pfs: connect to the backend

Implement functions to handle the xenbus handshake. Upon connection, allocate the rings according to the protocol specification. Initialize a work_struct and a wait_queue. The work_struct will be used to schedule work upon receiving an event channel notification from the backend. The wait_queue

[PATCH v3 2/7] xen: introduce the header file for the Xen 9pfs transport protocol

It uses the new ring.h macros to declare rings and interfaces. Signed-off-by: Stefano Stabellini CC: konrad.w...@oracle.com CC: boris.ostrov...@oracle.com CC: jgr...@suse.com --- include/xen/interface/io/9pfs.h | 40 1 file changed,

[PATCH v3 4/7] xen/9pfs: connect to the backend

Implement functions to handle the xenbus handshake. Upon connection, allocate the rings according to the protocol specification. Initialize a work_struct and a wait_queue. The work_struct will be used to schedule work upon receiving an event channel notification from the backend. The wait_queue

[PATCH v3 2/7] xen: introduce the header file for the Xen 9pfs transport protocol

It uses the new ring.h macros to declare rings and interfaces. Signed-off-by: Stefano Stabellini CC: konrad.w...@oracle.com CC: boris.ostrov...@oracle.com CC: jgr...@suse.com --- include/xen/interface/io/9pfs.h | 40 1 file changed, 40 insertions(+)

[PATCH v3 1/7] xen: import new ring macros in ring.h

Sync the ring.h file with upstream Xen, to introduce the new ring macros. They will be used by the Xen transport for 9pfs. Signed-off-by: Stefano Stabellini CC: konrad.w...@oracle.com CC: boris.ostrov...@oracle.com CC: jgr...@suse.com --- NB: The new macros have not been

[PATCH v3 1/7] xen: import new ring macros in ring.h

Sync the ring.h file with upstream Xen, to introduce the new ring macros. They will be used by the Xen transport for 9pfs. Signed-off-by: Stefano Stabellini CC: konrad.w...@oracle.com CC: boris.ostrov...@oracle.com CC: jgr...@suse.com --- NB: The new macros have not been committed to Xen yet.

[PATCH v3 3/7] xen/9pfs: introduce Xen 9pfs transport driver

Introduce the Xen 9pfs transport driver: add struct xenbus_driver to register as a xenbus driver and add struct p9_trans_module to register as v9fs driver. All functions are empty stubs for now. Signed-off-by: Stefano Stabellini Reviewed-by: Boris Ostrovsky

[PATCH v3 3/7] xen/9pfs: introduce Xen 9pfs transport driver

Introduce the Xen 9pfs transport driver: add struct xenbus_driver to register as a xenbus driver and add struct p9_trans_module to register as v9fs driver. All functions are empty stubs for now. Signed-off-by: Stefano Stabellini Reviewed-by: Boris Ostrovsky CC: jgr...@suse.com CC: Eric Van

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Greg KH, on mar. 14 mars 2017 07:43:03 +0800, wrote: > > Well, for a start that didn't exist when Okash worked on the TTY part :) > > Fair enough, but it has been discussed for many months now on the > linux-serial mailing list. I have not had time for years to actually work on this subject, so

[PATCH v3 0/7] Xen transport for 9pfs frontend driver

Hi all, This patch series implements a new transport for 9pfs, aimed at Xen systems. The transport is based on a traditional Xen frontend and backend drivers pair. This patch series implements the frontend, which typically runs in a regular unprivileged guest. I also sent a series that

Re: [patch 0/7] staging: speakup: introduce tty-based comms

Greg KH, on mar. 14 mars 2017 07:43:03 +0800, wrote: > > Well, for a start that didn't exist when Okash worked on the TTY part :) > > Fair enough, but it has been discussed for many months now on the > linux-serial mailing list. I have not had time for years to actually work on this subject, so

[PATCH v3 0/7] Xen transport for 9pfs frontend driver

Hi all, This patch series implements a new transport for 9pfs, aimed at Xen systems. The transport is based on a traditional Xen frontend and backend drivers pair. This patch series implements the frontend, which typically runs in a regular unprivileged guest. I also sent a series that

[PATCH v3] kvm: better MWAIT emulation for guests

Guests running Mac OS 5, 6, and 7 (Leopard through Lion) have a problem: unless explicitly provided with kernel command line argument "idlehalt=0" they'd implicitly assume MONITOR and MWAIT availability, without checking CPUID. We currently emulate that as a NOP but on VMX we can do better: let

[PATCH v3] kvm: better MWAIT emulation for guests

Guests running Mac OS 5, 6, and 7 (Leopard through Lion) have a problem: unless explicitly provided with kernel command line argument "idlehalt=0" they'd implicitly assume MONITOR and MWAIT availability, without checking CPUID. We currently emulate that as a NOP but on VMX we can do better: let

Re: [RFC] powerpc: handle simultanneous interrupts at once

On Fri, 2017-03-10 at 12:11 +0100, Christophe Leroy wrote: > It often happens to have simultanneous interrupts, for instance > when having double Ethernet attachment. With the current > implementation, we suffer the cost of kernel entry/exit for each > interrupt. > > This patch introduces a loop

Re: [RFC] powerpc: handle simultanneous interrupts at once

On Fri, 2017-03-10 at 12:11 +0100, Christophe Leroy wrote: > It often happens to have simultanneous interrupts, for instance > when having double Ethernet attachment. With the current > implementation, we suffer the cost of kernel entry/exit for each > interrupt. > > This patch introduces a loop

Re: [patch 0/7] staging: speakup: introduce tty-based comms

On Mon, Mar 13, 2017 at 11:26:08PM +0100, Samuel Thibault wrote: > Hello, > > Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote: > > On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > > > This patchset introduces a TTY-based way for the synths to communicate > > > with

Re: [patch 0/7] staging: speakup: introduce tty-based comms

On Mon, Mar 13, 2017 at 11:26:08PM +0100, Samuel Thibault wrote: > Hello, > > Greg KH, on mar. 14 mars 2017 06:14:04 +0800, wrote: > > On Mon, Mar 13, 2017 at 10:05:51PM +, okash.khaw...@gmail.com wrote: > > > This patchset introduces a TTY-based way for the synths to communicate > > > with

[PATCH v3] phy: rcar-gen3-usb2: fix implementation for runtime PM

This patch fixes an issue that this driver doesn't take care of the runtime PM. This code assumed that devm_phy_create() called pm_runtime_enable(dev), but it misunderstood the dev_phy_create()'s specification. This driver should call its own pm_runtime_enable() before dev_phy_create(). Fixes:

[PATCH v3] phy: rcar-gen3-usb2: fix implementation for runtime PM

This patch fixes an issue that this driver doesn't take care of the runtime PM. This code assumed that devm_phy_create() called pm_runtime_enable(dev), but it misunderstood the dev_phy_create()'s specification. This driver should call its own pm_runtime_enable() before dev_phy_create(). Fixes:

RE: [PATCH v2] phy: rcar-gen3-usb2: fix implementation for runtime PM

Hi! > From: Sergei Shtylyov > Sent: Monday, March 13, 2017 8:57 PM > > On 03/13/2017 12:39 PM, Yoshihiro Shimoda wrote: > > > This patch fixes an issue that this driver doesn't take care of the runtime > > PM. This code assumed that devm_phy_create() called pm_runtime_enable(dev), > > but it

RE: [PATCH v2] phy: rcar-gen3-usb2: fix implementation for runtime PM

Hi! > From: Sergei Shtylyov > Sent: Monday, March 13, 2017 8:57 PM > > On 03/13/2017 12:39 PM, Yoshihiro Shimoda wrote: > > > This patch fixes an issue that this driver doesn't take care of the runtime > > PM. This code assumed that devm_phy_create() called pm_runtime_enable(dev), > > but it

Re: [PATCH v5 00/39] i.MX Media Driver

er, I meant I will integrate this patch. And verify/fix possible breakage for non-bayer passthrough. Steve On 03/13/2017 02:30 AM, Russell King - ARM Linux wrote: On Mon, Mar 13, 2017 at 08:16:25AM +, Russell King - ARM Linux wrote: On Sun, Mar 12, 2017 at 09:26:41PM -0700, Steve

Re: [PATCH v5 00/39] i.MX Media Driver

er, I meant I will integrate this patch. And verify/fix possible breakage for non-bayer passthrough. Steve On 03/13/2017 02:30 AM, Russell King - ARM Linux wrote: On Mon, Mar 13, 2017 at 08:16:25AM +, Russell King - ARM Linux wrote: On Sun, Mar 12, 2017 at 09:26:41PM -0700, Steve

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/13/2017 01:16 AM, Russell King - ARM Linux wrote: On Sun, Mar 12, 2017 at 09:26:41PM -0700, Steve Longerbeam wrote: On 03/12/2017 01:22 PM, Russell King - ARM Linux wrote: What I had was this patch for your v3. I never got to testing your v4 because of the LP-11 problem. In v5,

Re: [PATCH v5 00/39] i.MX Media Driver

On 03/13/2017 01:16 AM, Russell King - ARM Linux wrote: On Sun, Mar 12, 2017 at 09:26:41PM -0700, Steve Longerbeam wrote: On 03/12/2017 01:22 PM, Russell King - ARM Linux wrote: What I had was this patch for your v3. I never got to testing your v4 because of the LP-11 problem. In v5,

Re: [PATCH v3] extcon: int3496: Set the id pin to direction-input if necessary

Hi, On 2017년 03월 13일 20:28, Hans de Goede wrote: > With the new more strict ACPI gpio code the dsdt's IoRestriction > flags are honored on gpiod_get, but in some dsdt's it is wrong, > so explicitly call gpiod_direction_input on the id gpio if > necessary. > > This fixes the following errors when

Re: [PATCH v3] extcon: int3496: Set the id pin to direction-input if necessary

Hi, On 2017년 03월 13일 20:28, Hans de Goede wrote: > With the new more strict ACPI gpio code the dsdt's IoRestriction > flags are honored on gpiod_get, but in some dsdt's it is wrong, > so explicitly call gpiod_direction_input on the id gpio if > necessary. > > This fixes the following errors when

Re: [PATCH 1/4] Documentation: hid: fix path to input bus definitions

On Sun, 12 Mar 2017 12:54:21 +0100 Martin Kepplinger wrote: > The UAPI header split failed to update the documentation here; fix things > accordingly. I've applied all four to the docs tree, thanks. jon

Re: [PATCH 1/4] Documentation: hid: fix path to input bus definitions

On Sun, 12 Mar 2017 12:54:21 +0100 Martin Kepplinger wrote: > The UAPI header split failed to update the documentation here; fix things > accordingly. I've applied all four to the docs tree, thanks. jon

Re: [RFC 1/2] fanotify: new event FAN_MODIFY_DIR

An example userspace program that uses FAN_MODIFY_DIR to reliably keep an up-to-date internal representation of the file system. It uses some filehandle trickery to identify inodes, other heuristics could be also used. --- //#define _GNU_SOURCE #include #include #include #include #include

Re: WTH is going on with memory hotplug sysf interface (was: Re: [RFC PATCH] mm, hotplug: get rid of auto_online_blocks)

> and ARCH_SPARSEMEM_DEFAULT is enabeld on 64b. So I guess whatever was > the reason to add this code back in 2006 is not true anymore. So I am > really wondering. Do we absolutely need to assign pages which are not > onlined yet to the ZONE_NORMAL unconditionally? Why cannot we put them > out of

Re: [RFC 1/2] fanotify: new event FAN_MODIFY_DIR

An example userspace program that uses FAN_MODIFY_DIR to reliably keep an up-to-date internal representation of the file system. It uses some filehandle trickery to identify inodes, other heuristics could be also used. --- //#define _GNU_SOURCE #include #include #include #include #include

Re: WTH is going on with memory hotplug sysf interface (was: Re: [RFC PATCH] mm, hotplug: get rid of auto_online_blocks)

> and ARCH_SPARSEMEM_DEFAULT is enabeld on 64b. So I guess whatever was > the reason to add this code back in 2006 is not true anymore. So I am > really wondering. Do we absolutely need to assign pages which are not > onlined yet to the ZONE_NORMAL unconditionally? Why cannot we put them > out of

Re: [GIT PULL 6/7] ARM: 64-bit DT updates for v4.11

Hi, On Thu, Feb 23, 2017 at 03:20:19PM -0800, Neil Armstrong wrote: > On 02/23/2017 03:10 PM, Arnd Bergmann wrote: > > The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: > > > > Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) > > > > are available in the git repository

Re: [GIT PULL 6/7] ARM: 64-bit DT updates for v4.11

Hi, On Thu, Feb 23, 2017 at 03:20:19PM -0800, Neil Armstrong wrote: > On 02/23/2017 03:10 PM, Arnd Bergmann wrote: > > The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8: > > > > Linux 4.10-rc3 (2017-01-08 14:18:17 -0800) > > > > are available in the git repository

[RFC 2/2] fanotify: emit FAN_MODIFY_DIR on filesystem changes

Besause fanotify requires `struct path`, the event cannot be generated directly in `fsnotify_move` and friends because they only get the inode (and their callers, `vfs_rename` cannot supply any better info). So instead it needs to be generated higher in the call chain, i.e. in the callers of

[RFC 2/2] fanotify: emit FAN_MODIFY_DIR on filesystem changes

Besause fanotify requires `struct path`, the event cannot be generated directly in `fsnotify_move` and friends because they only get the inode (and their callers, `vfs_rename` cannot supply any better info). So instead it needs to be generated higher in the call chain, i.e. in the callers of

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