From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, kubakici@wp.pl, oss-drivers@netronome.com
Subject: Re: [PATCH net-next 00/12] Netronome NFP4000 and NFP6000 PF driver
Date: Fri, 10 Feb 2017 15:53:52 -0500 (EST) [thread overview]
Message-ID: <20170210.155352.2076111009943025495.davem@davemloft.net> (raw)
In-Reply-To: <20170209171738.17386-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Thu, 9 Feb 2017 09:17:26 -0800
> This is a base PF driver for Netronome NFP4000 and NFP6000 chips. This
> series doesn't add any exciting new features, it provides a foundation
> for supporting more advanced firmware applications.
Series applied, thank you.
prev parent reply other threads:[~2017-02-10 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 17:17 [PATCH net-next 00/12] Netronome NFP4000 and NFP6000 PF driver Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 01/12] bitfield.h: add FIELD_FIT() helper Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 02/12] nfp: rename the driver and add new main file Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 03/12] nfp: add CPP access core Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 04/12] nfp: add support for resources Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 05/12] nfp: add hwinfo support Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 06/12] nfp: add support for reading nffw info Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 07/12] nfp: add MIP reading support Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 08/12] nfp: add rtsym support Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 09/12] nfp: add support for service processor access Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 10/12] nfp: add port layer to debugfs directories Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 11/12] nfp: allocate irqs in lower driver Jakub Kicinski
2017-02-09 17:17 ` [PATCH net-next 12/12] nfp: add the PF driver Jakub Kicinski
2017-02-10 20:53 ` 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=20170210.155352.2076111009943025495.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=kubakici@wp.pl \
--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).