From: Johan Hovold <johan@kernel.org>
To: Daniele Palmas <dnlplm@gmail.com>
Cc: Johan Hovold <johan@kernel.org>, linux-usb@vger.kernel.org
Subject: [v2,1/1] USB: serial: option: add Telit ME910 ECM composition
Date: Wed, 20 Feb 2019 12:04:10 +0100 [thread overview]
Message-ID: <20190220110410.GJ4072@localhost> (raw)
On Wed, Feb 20, 2019 at 11:43:17AM +0100, Daniele Palmas wrote:
> This patch adds Telit ME910 family ECM composition 0x1102.
>
> Signed-off-by: Daniele Palmas <dnlplm@gmail.com>
> ---
> v2: add matching on interface class to remove blacklisting
>
> lsusb verbose output:
> ---
> drivers/usb/serial/option.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
> index aef15497ff31..f6674fb7269a 100644
> --- a/drivers/usb/serial/option.c
> +++ b/drivers/usb/serial/option.c
> @@ -1148,6 +1148,8 @@ static const struct usb_device_id option_ids[] = {
> .driver_info = NCTRL(0) | RSVD(1) | RSVD(3) },
> { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_ME910_DUAL_MODEM),
> .driver_info = NCTRL(0) | RSVD(3) },
> + { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1102, 0xff),
> + .driver_info = NCTRL(0) }, /* TELIT ME910 (ECM) */
I moved the comment to the USB_DEVICE line for consistency with the
other entries (it's ok to break the 80 col rule here).
> { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_LE910),
> .driver_info = NCTRL(0) | RSVD(1) | RSVD(2) },
> { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_LE910_USBCFG4),
Now applied.
Thanks,
Johan
next reply other threads:[~2019-02-20 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 11:04 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-20 10:43 [v2,1/1] USB: serial: option: add Telit ME910 ECM composition Daniele Palmas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190220110410.GJ4072@localhost \
--to=johan@kernel.org \
--cc=dnlplm@gmail.com \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.