From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net-next 0/4] nfp: dead code, clean ups and slight improvements
Date: Mon, 11 Dec 2017 12:12:58 -0500 (EST) [thread overview]
Message-ID: <20171211.121258.1749866214646940088.davem@davemloft.net> (raw)
In-Reply-To: <20171209033704.5553-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Fri, 8 Dec 2017 19:37:00 -0800
> This series contains small clean ups from John and Carl, and brings
> no functional changes.
>
> John's improvements target the flower code. First he makes sure we don't
> allocate space in FW request messages for MAC matches if the TC rule does
> not contain any. The remaining two patches remove some dead code and
> unused defines.
>
> Carl follows up with a slight optimization to his recent ethtool FW state
> dumps, byte swapping input parameters once instead of the data for every
> dumped item.
Series applied, thanks.
prev parent reply other threads:[~2017-12-11 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 3:37 [PATCH net-next 0/4] nfp: dead code, clean ups and slight improvements Jakub Kicinski
2017-12-09 3:37 ` [PATCH net-next 1/4] nfp: flower: do not assume mac/mpls matches Jakub Kicinski
2017-12-09 3:37 ` [PATCH net-next 2/4] nfp: flower: remove dead code paths Jakub Kicinski
2017-12-09 3:37 ` [PATCH net-next 3/4] nfp: flower: remove unused defines Jakub Kicinski
2017-12-09 3:37 ` [PATCH net-next 4/4] nfp: debug dump - decrease endian conversions Jakub Kicinski
2017-12-11 17:12 ` 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=20171211.121258.1749866214646940088.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).