From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/3] nfp: fixes and trivial cleanup
Date: Thu, 08 Sep 2016 17:18:57 -0700 (PDT) [thread overview]
Message-ID: <20160908.171857.762759573997622959.davem@davemloft.net> (raw)
In-Reply-To: <1473273937-9230-1-git-send-email-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Wed, 7 Sep 2016 19:45:34 +0100
> First patch drops unnecessary version.h includes. Second one
> drops support for pre-release versions of FW ABI. Removing
> FW ABI 0.0 from supported set is particularly good since 0
> could just be uninitialized memory. Last but not least I drop
> unnecessary padding of frames on RX which makes us count bytes
> incorrectly for the VF2VF traffic.
Series applied, thanks.
prev parent reply other threads:[~2016-09-09 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 18:45 [PATCH net 0/3] nfp: fixes and trivial cleanup Jakub Kicinski
2016-09-07 18:45 ` [PATCH net 1/3] nfp: remove linux/version.h includes Jakub Kicinski
2016-09-07 18:45 ` [PATCH net 2/3] nfp: drop support for old firmware ABIs Jakub Kicinski
2016-09-07 18:45 ` [PATCH net 3/3] nfp: don't pad frames on receive Jakub Kicinski
2016-09-09 0: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=20160908.171857.762759573997622959.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.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).