From: "Bjørn Mork" <bjorn@mork.no>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-usb@vger.kernel.org,
Network Development <netdev@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Matthias Urlichs <smurf@smurf.noris.de>,
dagofthedofg@gmail.com
Subject: Re: [PATCH] usb: add device IDs for Dell 5804 (Novatel E371) WWAN card
Date: Wed, 01 May 2013 22:19:28 +0200 [thread overview]
Message-ID: <87mwsebghb.fsf@nemi.mork.no> (raw)
In-Reply-To: <1367438620.12353.11.camel@dcbw.foobar.com> (Dan Williams's message of "Wed, 01 May 2013 15:03:40 -0500")
Dan Williams <dcbw@redhat.com> writes:
> On Wed, 2013-05-01 at 20:33 +0200, Bjørn Mork wrote:
>> Dan Williams <dcbw@redhat.com> writes:
>>
>> > A rebranded Novatel E371 for AT&T's LTE bands.
>>
>> I don't think we're handling the Novatel branded E371 yet? I tried
>> googling for ID of that, but were unable to find it. I guess you don't
>> know either... Well, nothing we can do about that until someone reports
>> it.
>
> See the referenced bug report which prompted this:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=955426
>
> It's definitely QMI capable.
Yes, absolutely.
I just assumed the E371 exists with a Novatel vendor ID as well. Which
we could and should also add, if we only knew what the product ID is.
But it wasn't my intention to question the addition of the Dell
rebranded E371. There's absolutely no need to let that wait. Sorry for
being unclear. I am not communicating well today...
Bjørn
next prev parent reply other threads:[~2013-05-01 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 18:01 [PATCH] usb: add device IDs for Dell 5804 (Novatel E371) WWAN card Dan Williams
[not found] ` <1367431305.12353.8.camel-wKZy7rqYPVb5EHUCmHmTqw@public.gmane.org>
2013-05-01 18:33 ` Bjørn Mork
2013-05-01 18:42 ` David Miller
2013-05-01 20:04 ` Dan Williams
2013-05-01 20:03 ` Dan Williams
2013-05-01 20:19 ` Bjørn Mork [this message]
2013-05-01 20:22 ` dag dg
[not found] ` <CAO2Qn5m08QOBJfuvR1xAF9msw2WX0mAT64=s8VmXuO41h9dkWg@mail.gmail.com>
2013-05-01 20:24 ` Dan Williams
2013-05-01 20:24 ` dag dg
2013-05-01 20:28 ` Dan Williams
2013-05-01 20:24 ` Dan Williams
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=87mwsebghb.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=dagofthedofg@gmail.com \
--cc=dcbw@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=smurf@smurf.noris.de \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox