netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bjorn@mork.no
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org, oneukum@suse.de
Subject: Re: [PATCH net-next 0/5] cdc_mbim + qmi_wwan trivial fixes
Date: Mon, 04 Nov 2013 15:48:42 -0500 (EST)	[thread overview]
Message-ID: <20131104.154842.937373087218100293.davem@davemloft.net> (raw)
In-Reply-To: <1383311936-20954-1-git-send-email-bjorn@mork.no>

From: Bjørn Mork <bjorn@mork.no>
Date: Fri,  1 Nov 2013 14:18:51 +0100

> This series fixes three problems Oliver pointed out during the
> review of the new huawei_cdc_ncm driver:
> http://patchwork.ozlabs.org/patch/278903/
> 
> That innocent driver only used cdc_mbim as a blueprint, and
> all the blame should really have gone to me....
> 
> I do have a similar fix for the manage_power issue in the
> cdc-wdm USB class driver as well.  It will be submitted to
> linux-usb as soon as Greg opens up his mailbox again :-)

Looks good, applied, thanks.

      parent reply	other threads:[~2013-11-04 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 13:18 [PATCH net-next 0/5] cdc_mbim + qmi_wwan trivial fixes Bjørn Mork
     [not found] ` <1383311936-20954-1-git-send-email-bjorn-yOkvZcmFvRU@public.gmane.org>
2013-11-01 13:18   ` [PATCH net-next 1/5] net: cdc_mbim: manage_power should always set needs_remote_wakeup Bjørn Mork
2013-11-01 13:18   ` [PATCH net-next 2/5] net: qmi_wwan: " Bjørn Mork
2013-11-01 13:18   ` [PATCH net-next 5/5] net: cdc_mbim: fixup error return value Bjørn Mork
2013-11-01 13:18 ` [PATCH net-next 3/5] net: qmi_wwan: no need to check for resume if suspend exists Bjørn Mork
2013-11-01 13:18 ` [PATCH net-next 4/5] net: cdc_mbim: " Bjørn Mork
2013-11-04 20:48 ` David Miller [this message]

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=20131104.154842.937373087218100293.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bjorn@mork.no \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).