netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mrkiko.rs@gmail.com
Cc: linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH V3] cdc_ncm: Add support for moving NDP to end of NCM frame
Date: Thu, 09 Jul 2015 14:58:55 -0700 (PDT)	[thread overview]
Message-ID: <20150709.145855.25174711066333213.davem@davemloft.net> (raw)
In-Reply-To: <1436353557-1959-1-git-send-email-mrkiko.rs@gmail.com>

From: Enrico Mioso <mrkiko.rs@gmail.com>
Date: Wed,  8 Jul 2015 13:05:57 +0200

> NCM specs are not actually mandating a specific position in the frame for
> the NDP (Network Datagram Pointer). However, some Huawei devices will
> ignore our aggregates if it is not placed after the datagrams it points
> to. Add support for doing just this, in a per-device configurable way.
> While at it, update NCM subdrivers, disabling this functionality in all of
> them, except in huawei_cdc_ncm where it is enabled instead.
> We aren't making any distinction between different Huawei NCM devices,
> based on what the vendor driver does. Standard NCM devices are left
> unaffected: if they are compliant, they should be always usable, still
> stay on the safe side.
> 
> This change has been tested and working with a Huawei E3131 device (which
> works regardless of NDP position), a Huawei E3531 (also working both
> ways) and an E3372 (which mandates NDP to be after indexed datagrams).
> 
> V1->V2:
> - corrected wrong NDP acronym definition
> - fixed possible NULL pointer dereference
> - patch cleanup
> V2->V3:
> - Properly account for the NDP size when writing new packets to SKB
> 
> Signed-off-by: Enrico Mioso <mrkiko.rs@gmail.com>

Applied, thanks.

  reply	other threads:[~2015-07-09 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 11:05 [PATCH V3] cdc_ncm: Add support for moving NDP to end of NCM frame Enrico Mioso
2015-07-09 21:58 ` David Miller [this message]
     [not found] <00f181fc416046b5f3ea83b445ef85fe@apollo.open-resource.org>
     [not found] ` <5592E970.4020401@elisanet.fi>
     [not found]   ` <75c1cffa49f050004339554141dfde77@apollo.open-resource.org>
     [not found]     ` <alpine.LNX.2.20.1507030739360.1735@localhost.localdomain>
     [not found]       ` <2bf03dff3347d3745f35225e77581ef5@apollo.open-resource.org>
2015-07-09 13:11         ` chrono

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=20150709.145855.25174711066333213.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-usb@vger.kernel.org \
    --cc=mrkiko.rs@gmail.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).