Netdev List
 help / color / mirror / Atom feed
From: Bert Kenward <bkenward@solarflare.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
	David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>, Edward Cree <ecree@solarflare.com>
Subject: Re: [PATCH net-next] sfc: remove napi_hash_del() call
Date: Wed, 16 Nov 2016 14:15:05 +0000	[thread overview]
Message-ID: <346f2de7-ef32-e60f-fe1d-d2eae0071636@solarflare.com> (raw)
In-Reply-To: <1479304907.8455.171.camel@edumazet-glaptop3.roam.corp.google.com>

On 16/11/16 14:01, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> Calling napi_hash_del() after netif_napi_del() is pointless.
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Edward Cree <ecree@solarflare.com>
> Cc: Bert Kenward <bkenward@solarflare.com>
> ---
>  drivers/net/ethernet/sfc/efx.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)

Acked-by: Bert Kenward <bkenward@solarflare.com>

  reply	other threads:[~2016-11-16 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 14:01 [PATCH net-next] sfc: remove napi_hash_del() call Eric Dumazet
2016-11-16 14:15 ` Bert Kenward [this message]
2016-11-16 22:05 ` David Miller

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=346f2de7-ef32-e60f-fe1d-d2eae0071636@solarflare.com \
    --to=bkenward@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.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