Re:Confirm Receipt of My Message

Dear Respectfully, My name is Abla Yusuf from Syria,please i need your urgent assistance to help me and my two daughters relocate out of Syria because of the recent bombing by president Trump and his intentions to bomb more..I need you to help us relocate including our belongings and funds for

Re: UDC ep0 desc or no desc

On Sat, 23 Jun 2018, Benjamin Herrenschmidt wrote: > Hi folks ! > > I noticed some UDC drivers setup a "desc" pointer for ep0.desc for the > driver, some don't. > > Is it officially needed ? No, it isn't. The only "core" routine that requires a desc pointer in the endpoint structure is usb_ep

[PATCH] usb: serial: qcserial: add support for the Dell DW5821e module

This module exposes two USB configurations: a QMI+AT capable setup on USB config #1 and a MBIM capable setup on USB config #2. By default the kernel will choose the MBIM capable configuration as long as the cdc_mbim driver is available. This patch adds support for the serial ports in the secondary

[PATCH 01/12] usb: serial: cyberjack: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 03/12] usb: serial: io_edgeport: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 00/12] usb: serial: Use irqsave in USB's complete callback

This is about using _irqsave() primitives in the completion callback in order to get rid of local_irq_save() in __usb_hcd_giveback_urb(). Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH 02/12] usb: serial: digi_acceleport: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 08/12] usb: serial: sierra: disable irq's for portdata lock

From: John Ogness The portdata spinlock can be taken in interrupt context (via sierra_outdat_callback()). Disable interrupts when taking the portdata spinlock. Cc: Johan Hovold Cc: Greg Kroah-Hartman Signed-off-by: John Ogness Signed-off-by: Sebastian Andrzej Siewior --- drivers/usb/serial/

[PATCH 07/12] usb: serial: quatech2: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 05/12] usb: serial: mos7720: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 04/12] usb: serial: io_ti: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 09/12] usb: serial: sierra: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 12/12] usb: serial: usb_wwan: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 11/12] usb: serial: ti_usb_3410_5052: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 06/12] usb: serial: mos7840: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

[PATCH 10/12] usb: serial: symbolserial: use irqsave() in USB's complete callback

From: John Ogness The USB completion callback does not disable interrupts while acquiring the lock. We want to remove the local_irq_disable() invocation from __usb_hcd_giveback_urb() and therefore it is required for the callback handler to disable the interrupts while acquiring the lock. The call

Re: UDC ep0 desc or no desc

On Sat, 2018-06-23 at 11:07 -0400, Alan Stern wrote: > On Sat, 23 Jun 2018, Benjamin Herrenschmidt wrote: > > > Hi folks ! > > > > I noticed some UDC drivers setup a "desc" pointer for ep0.desc for the > > driver, some don't. > > > > Is it officially needed ? > > No, it isn't. The only "core"