Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bjorn@mork.no
Cc: netdev@vger.kernel.org, alexey.orishko@gmail.com, gsuarez@smithmicro.com
Subject: Re: [PATCH net-next 0/2] cdc_mbim workarounds for firmware bugs
Date: Sat, 02 Nov 2013 01:30:12 -0400 (EDT)	[thread overview]
Message-ID: <20131102.013012.722023816896482451.davem@davemloft.net> (raw)
In-Reply-To: <1383231371-8098-1-git-send-email-bjorn@mork.no>

From: Bjørn Mork <bjorn@mork.no>
Date: Thu, 31 Oct 2013 15:56:09 +0100

> The first patch is an attempt to work around a bug which prevents
> some devices from working with IPv6. I guess handling ND in a driver
> can be considered controversial, but it was the best alternative I
> came up with.
> 
> The second is the "final solution" to the well known ZLP bug, which
> as we feared is present in a number of devices using different
> vendor IDs. Enabling this is definitely controversial, but I do not
> see any other possible solution.  The blacklist has become
> unmanagable, and I am pretty sure it is very incomplete due to
> under-reporting.  Devices known to work without ZLPs can be added
> to the whitelist.

This seems fine, both applied, thanks.

      parent reply	other threads:[~2013-11-02  5:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 14:56 [PATCH net-next 0/2] cdc_mbim workarounds for firmware bugs Bjørn Mork
2013-10-31 14:56 ` [PATCH net-next 1/2] net: cdc_mbim: handle IPv6 Neigbor Solicitations Bjørn Mork
2013-10-31 14:56 ` [PATCH net-next 2/2] net: cdc_mbim: change the default to send ZLPs Bjørn Mork
2013-11-02  5:30 ` 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=20131102.013012.722023816896482451.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexey.orishko@gmail.com \
    --cc=bjorn@mork.no \
    --cc=gsuarez@smithmicro.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