netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net 0/4] nfp: fix a warning, stats, naming and route leak
Date: Tue, 12 Jun 2018 15:18:44 -0700 (PDT)	[thread overview]
Message-ID: <20180612.151844.844050004457452789.davem@davemloft.net> (raw)
In-Reply-To: <20180612043338.5447-1-jakub.kicinski@netronome.com>

From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Mon, 11 Jun 2018 21:33:34 -0700

> Various fixes for the NFP.  Patch 1 fixes a harmless GCC 8 warning.
> Patch 2 ensures statistics are correct after users decrease the number
> of channels/rings.  Patch 3 restores phy_port_name behaviour for flower,
> ndo_get_phy_port_name used to return -EOPNOTSUPP on one of the netdevs,
> and we need to keep it that way otherwise interface names may change.
> Patch 4 fixes refcnt leak in flower tunnel offload code.

Series applied.

      parent reply	other threads:[~2018-06-12 22:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  4:33 [PATCH net 0/4] nfp: fix a warning, stats, naming and route leak Jakub Kicinski
2018-06-12  4:33 ` [PATCH net 1/4] nfp: don't pad strings in nfp_cpp_resource_find() to avoid gcc 8 warning Jakub Kicinski
2018-06-12  4:33 ` [PATCH net 2/4] nfp: include all ring counters in interface stats Jakub Kicinski
2018-06-12  4:33 ` [PATCH net 3/4] nfp: remove phys_port_name on flower's vNIC Jakub Kicinski
2018-06-12  4:33 ` [PATCH net 4/4] nfp: flower: free dst_entry in route table Jakub Kicinski
2018-06-12 22:18 ` 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=20180612.151844.844050004457452789.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    /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).