netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCHv3 net 0/5] nfp: MTU fixes for net
Date: Thu, 18 Feb 2016 20:38:08 +0000	[thread overview]
Message-ID: <1455827893-26366-1-git-send-email-jakub.kicinski@netronome.com> (raw)

Hi Dave!

This is the first part of MTU reconfiguration fixes.  These
are the patches which I would like to get into -net.  The
requested overhaul of the way MTU configuration is done is
posted as a separate series targeted at net-next.

Thanks!


Jakub Kicinski (5):
  nfp: return error if MTU change fails
  nfp: free buffers before changing MTU
  nfp: correct RX buffer length calculation
  nfp: fix RX buffer length validation
  nfp: don't trust netif_running() in debug code

 .../net/ethernet/netronome/nfp/nfp_net_common.c    | 42 ++++++++++------------
 .../net/ethernet/netronome/nfp/nfp_net_debugfs.c   |  4 +--
 2 files changed, 20 insertions(+), 26 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-02-18 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 20:38 Jakub Kicinski [this message]
2016-02-18 20:38 ` [PATCHv3 net 1/5] nfp: return error if MTU change fails Jakub Kicinski
2016-02-18 20:38 ` [PATCHv3 net 2/5] nfp: free buffers before changing MTU Jakub Kicinski
2016-02-18 20:38 ` [PATCHv3 net 3/5] nfp: correct RX buffer length calculation Jakub Kicinski
2016-02-18 20:38 ` [PATCHv3 net 4/5] nfp: fix RX buffer length validation Jakub Kicinski
2016-02-18 20:38 ` [PATCHv3 net 5/5] nfp: don't trust netif_running() in debug code Jakub Kicinski
2016-02-20  5:01   ` David Miller
2016-02-20 10:51     ` Jakub Kicinski

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=1455827893-26366-1-git-send-email-jakub.kicinski@netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=davem@davemloft.net \
    --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).