From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 00/12] net: get rid of __napi_complete()
Date: Sun, 05 Feb 2017 17:16:32 -0500 (EST) [thread overview]
Message-ID: <20170205.171632.491203678628144671.davem@davemloft.net> (raw)
In-Reply-To: <20170204232502.22361-1-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Sat, 4 Feb 2017 15:24:50 -0800
> This patch series removes __napi_complete() calls, in an effort
> to make NAPI API simpler and generalize GRO and napi_complete_done()
Nice cleanup, series applied, thanks Eric.
prev parent reply other threads:[~2017-02-05 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 23:24 [PATCH v2 net-next 00/12] net: get rid of __napi_complete() Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 01/12] 8139too: use napi_complete_done() Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 02/12] 8139cp: " Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 03/12] epic100: " Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 04/12] amd8111e: add GRO support Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 05/12] pcnet32: use napi_complete_done() Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 06/12] ep93xx_eth: add GRO support Eric Dumazet
2017-05-15 10:31 ` Lennert Buytenhek
2017-05-15 20:43 ` Ryan Mallon
2017-05-15 21:02 ` Alexander Sverdlin
2017-05-16 20:41 ` Alexander Sverdlin
2017-05-16 20:48 ` Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 07/12] skge: use napi_complete_done() Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 08/12] ks8695net: add GRO support Eric Dumazet
2017-02-04 23:24 ` [PATCH v2 net-next 09/12] qla3xxx: " Eric Dumazet
2017-02-04 23:25 ` [PATCH v2 net-next 10/12] ibm/emac: use napi_complete_done() Eric Dumazet
2017-02-04 23:25 ` [PATCH v2 net-next 11/12] aeroflex/greth: " Eric Dumazet
2017-02-04 23:25 ` [PATCH v2 net-next 12/12] net: remove __napi_complete() Eric Dumazet
2017-02-05 22:16 ` 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=20170205.171632.491203678628144671.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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).