public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft•net>
To: yanok@emcraft•com
Cc: sfr@canb•auug.org.au, linux-next@vger•kernel.org,
	bhutchings@solarflare•com
Subject: Re: [PATCH] dnet: replace obsolete *netif_rx_* functions with *napi_*
Date: Fri, 13 Mar 2009 09:51:57 -0700 (PDT)	[thread overview]
Message-ID: <20090313.095157.118123047.davem@davemloft.net> (raw)
In-Reply-To: <1236940253-4944-1-git-send-email-yanok@emcraft.com>

From: Ilya Yanok <yanok@emcraft•com>
Date: Fri, 13 Mar 2009 13:30:53 +0300

> *netif_rx_* functions is obsolete and removed in newer kernels so
> we need to use corresponding *napi_* functions instead.
> 
> Signed-off-by: Ilya Yanok <yanok@emcraft•com>

Applied, thanks.

  reply	other threads:[~2009-03-13 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13  2:16 linux-next: net-current/net tree build failure Stephen Rothwell
2009-03-13 10:30 ` [PATCH] dnet: replace obsolete *netif_rx_* functions with *napi_* Ilya Yanok
2009-03-13 16:51   ` David Miller [this message]
2009-03-13 17:23 ` linux-next: net-current/net tree build failure David Miller
2009-03-15 11:30   ` Stephen Rothwell

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=20090313.095157.118123047.davem@davemloft.net \
    --to=davem@davemloft$(echo .)net \
    --cc=bhutchings@solarflare$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=yanok@emcraft$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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