From: David Miller <davem@davemloft.net>
To: benchan@chromium.org
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, oliver@neukum.org,
gregkh@linuxfoundation.org, bjorn@mork.no,
gsuarez@smithmicro.com
Subject: Re: [PATCH net-next v4 0/2] adjust MTU as indicated by MBIM extended functional descriptor
Date: Thu, 20 Mar 2014 16:58:25 -0400 (EDT) [thread overview]
Message-ID: <20140320.165825.2258647784698720017.davem@davemloft.net> (raw)
In-Reply-To: <1395262806-19237-1-git-send-email-benchan@chromium.org>
From: Ben Chan <benchan@chromium.org>
Date: Wed, 19 Mar 2014 14:00:04 -0700
> The MBIM extended functional descriptor, defined in "Universal Serial Bus
> Communications Class Subclass Specification for Mobile Broadband Interface
> Model, Revision 1.0, Errata-1" by USB-IF, indicates the operator preferred MTU
> value via a wMTU field.
>
> This patch set ensures that the initial MTU value set by cdc_ncm on a MBIM net
> device does not exceed the wMTU value, provided the MBIM device exposes a MBIM
> extended functional descriptor.
>
> * Changelog
> v2: Fixed a le16_to_cpu conversion issue in patch 2/2 pointed out by
> Bjørn Mork <bjorn@mork.no>
> v3: No code changes. Resubmitted to include patch 1/2 as suggested by
> David Miller <davem@davemloft.net>
> v4: No code changes. Resubmitted as suggested by David Miller:
> - Added a summary of the patch set
> - Carried the ACK from Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> - Added a specified the tree (net-next) to apply the patch set to
Series applied to net-next, thanks Ben.
prev parent reply other threads:[~2014-03-20 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 21:00 Ben Chan
2014-03-19 21:00 ` [PATCH net-next v4 1/2] USB: cdc: add MBIM extended functional descriptor structure Ben Chan
2014-03-19 21:00 ` [PATCH net-next v4 2/2] net: cdc_ncm: respect operator preferred MTU reported by MBIM Ben Chan
2014-03-20 20:58 ` 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=20140320.165825.2258647784698720017.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benchan@chromium.org \
--cc=bjorn@mork.no \
--cc=gregkh@linuxfoundation.org \
--cc=gsuarez@smithmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.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
all inboxes | Powered by JetHome®