From: "David S. Miller" <davem@redhat.com>
To: dank@kegel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: napi backport to 2.4?
Date: Sun, 16 Jun 2002 22:26:55 -0700 (PDT) [thread overview]
Message-ID: <20020616.222655.24929541.davem@redhat.com> (raw)
In-Reply-To: <3D0D17AA.D0D11732@kegel.com>
From: dank@kegel.com
Date: Sun, 16 Jun 2002 15:56:42 -0700
How hard would it be to backport napi to 2.4?
There were a few rumblings about that last year...
I'll probably do it for 2.4.21 or some time around then...
prev parent reply other threads:[~2002-06-17 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 22:56 napi backport to 2.4? dank
2002-06-16 23:10 ` Jeff Garzik
2002-06-17 5:26 ` David S. 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=20020616.222655.24929541.davem@redhat.com \
--to=davem@redhat.com \
--cc=dank@kegel.com \
--cc=linux-kernel@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 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.