All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "David Miller" <davem@davemloft.net>,
	"Neil Horman" <nhorman@tuxdriver.com>,
	shemminger@vyatta.com, netdev@vger.kernel.org,
	"Krzysztof Hałasa" <khc@pm.waw.pl>
Subject: Re: [PATCH] net: Remove redundant NAPI functions
Date: Mon, 12 Jan 2009 07:13:17 +0000	[thread overview]
Message-ID: <20090112071317.GA4212@ff.dom.local> (raw)
In-Reply-To: <1231446610.3893.17.camel@achroite>

On Thu, Jan 08, 2009 at 08:30:10PM +0000, Ben Hutchings wrote:
> Following the removal of the unused struct net_device * parameter from
> the NAPI functions named *netif_rx_* in commit 908a7a1, they are
> exactly equivalent to the corresponding *napi_* functions and are
> therefore redundant.
> 
> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
> ---
...

Alas I wasn't able to send this earlier, but here is some issue
(I see Krzysztof tried to patch this too):

> diff --git a/drivers/net/wan/ixp4xx_hss.c b/drivers/net/wan/ixp4xx_hss.c
> index 2dc2416..9ea167b 100644
> --- a/drivers/net/wan/ixp4xx_hss.c
> +++ b/drivers/net/wan/ixp4xx_hss.c
> @@ -622,7 +622,7 @@ static void hss_hdlc_rx_irq(void *pdev)
>  	printk(KERN_DEBUG "%s: hss_hdlc_rx_irq\n", dev->name);
>  #endif
>  	qmgr_disable_irq(queue_ids[port->id].rx);
> -	netif_rx_schedule(dev, &port->napi);
> +	napi_schedule(dev, &port->napi);
>  }
>  
>  static int hss_hdlc_poll(struct napi_struct *napi, int budget)
> @@ -649,15 +649,15 @@ static int hss_hdlc_poll(struct napi_struct *napi, int budget)
>  		if ((n = queue_get_desc(rxq, port, 0)) < 0) {
>  #if DEBUG_RX
>  			printk(KERN_DEBUG "%s: hss_hdlc_poll"
> -			       " netif_rx_complete\n", dev->name);
> +			       " napi_complete\n", dev->name);
>  #endif
> -			netif_rx_complete(dev, napi);
> +			napi_complete(dev, napi);
>  			qmgr_enable_irq(rxq);
>  			if (!qmgr_stat_empty(rxq) &&
> -			    netif_rx_reschedule(napi)) {
> +			    napi_reschedule(napi)) {
>  #if DEBUG_RX
>  				printk(KERN_DEBUG "%s: hss_hdlc_poll"
> -				       " netif_rx_reschedule succeeded\n",
> +				       " napi_reschedule succeeded\n",
>  				       dev->name);
>  #endif
>  				qmgr_disable_irq(rxq);
> @@ -1069,7 +1069,7 @@ static int hss_hdlc_open(struct net_device *dev)
>  	hss_start_hdlc(port);
>  
>  	/* we may already have RX data, enables IRQ */
> -	netif_rx_schedule(dev, &port->napi);
> +	napi_schedule(dev, &port->napi);
>  	return 0;
>  
>  err_unlock:
...

Plus a missing chunk for: drivers/staging/benet/be_int.c.

Jarek P.

  parent reply	other threads:[~2009-01-12  7:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 20:30 [PATCH] net: Remove redundant NAPI functions Ben Hutchings
2009-01-08 20:40 ` Joe Perches
2009-01-08 20:54   ` David Miller
2009-01-09 14:58 ` Neil Horman
2009-01-10  7:06 ` David Miller
2009-01-12  7:13 ` Jarek Poplawski [this message]
2009-01-12 14:09   ` Ben Hutchings
2009-01-12 14:46     ` Ben Hutchings
2009-01-12 17:31       ` Krzysztof Halasa
2009-01-13  0:30         ` David Miller
2009-01-13  1:35           ` Krzysztof Halasa

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=20090112071317.GA4212@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=khc@pm.waw.pl \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.