From: Dan Williams
Date: Mon, 06 Jan 2014 15:39:40 -0600
> If the driver ever gets to that callback for any !Modem port, something
> is horribly wrong, which the BUG_ON() was attempting to make explicit.
> The driver only enables that callback for the Modem port, so yeah, it's
> somewhat defensiv
On Mon, 2014-01-06 at 16:30 -0500, David Miller wrote:
> From: Dan Williams
> Date: Mon, 06 Jan 2014 10:07:29 -0600
>
> > The existing serial state notification handling expected older Option
> > devices, having a hardcoded assumption that the Modem port was always
> > USB interface #2. That isn
From: Dan Williams
Date: Mon, 06 Jan 2014 10:07:29 -0600
> The existing serial state notification handling expected older Option
> devices, having a hardcoded assumption that the Modem port was always
> USB interface #2. That isn't true for devices from the past few years.
>
> hso_serial_state_
The existing serial state notification handling expected older Option
devices, having a hardcoded assumption that the Modem port was always
USB interface #2. That isn't true for devices from the past few years.
hso_serial_state_notification is a local cache of a USB Communications
Interface Class
4 matches
Mail list logo
