From: Jeff Garzik <jeff@garzik.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, hadi@cyberus.ca, rusty@rustcorp.com.au
Subject: Re: [PATCH RFC]: napi_struct V6
Date: Wed, 08 Aug 2007 12:27:35 -0400 [thread overview]
Message-ID: <46B9EEF7.7060009@garzik.org> (raw)
In-Reply-To: <20070808070628.284d805c@oldman>
Someone please make sure Documentation/networking/netdevices.txt remains
correct with regards to APIs and locking.
It -is- up to date, unlike NAPI howto. It should not change very much
due to this napi_struct work though, if at all.
Jeff
next prev parent reply other threads:[~2007-08-08 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 4:54 [PATCH RFC]: napi_struct V6 David Miller
2007-08-08 11:06 ` Stephen Hemminger
2007-08-08 16:27 ` Jeff Garzik [this message]
2007-08-08 23:18 ` David Miller
2007-08-09 4:36 ` 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=46B9EEF7.7060009@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@linux-foundation.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).