From: Dan Williams <dcbw@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: bjorn@mork.no, linux-usb@vger.kernel.org, netdev@vger.kernel.org,
gregkh@linuxfoundation.org, stable@vger.kernel.org,
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 15:04:03 -0500 [thread overview]
Message-ID: <1367438643.12353.12.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20130501.144241.1818296448373016452.davem@davemloft.net>
On Wed, 2013-05-01 at 14:42 -0400, David Miller wrote:
> From: Bjørn Mork <bjorn@mork.no>
> Date: Wed, 01 May 2013 20:33:10 +0200
>
> > 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.
> >
> > For the qmi_wwan part:
> > Acked-by: Bjørn Mork <bjorn@mork.no>
> >
> >
> >> diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
> >> index 558adfc..569caf6 100644
> >> --- a/drivers/usb/serial/option.c
> >> +++ b/drivers/usb/serial/option.c
> >
> > Combining net and usb patches in the same commit is probably not wise?
>
> Yes, this causes problems, please re-submit the networking portion all
> by itself.
Will do.
Dan
next prev parent reply other threads:[~2013-05-01 20:01 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 [this message]
2013-05-01 20:03 ` Dan Williams
2013-05-01 20:19 ` Bjørn Mork
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=1367438643.12353.12.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=bjorn@mork.no \
--cc=dagofthedofg@gmail.com \
--cc=davem@davemloft.net \
--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