From: Jarek Poplawski <jarkao2@o2.pl>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: "David S\. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] netdevice: kernel docbook addition
Date: Mon, 27 Aug 2007 14:18:53 +0200 [thread overview]
Message-ID: <20070827121853.GA2854@ff.dom.local> (raw)
In-Reply-To: <20070822123314.785dea2a@freepuppy.rosehill.hemminger.net>
On 22-08-2007 21:33, Stephen Hemminger wrote:
> Add more kernel doc's for part of the network device API.
> This is only a start, and needs more work.
>
> Applies against net-2.6.24
...
> +/**
> + * napi_disable - prevent NAPI from scheduling
> + * @n: napi context
> + *
> + * Resume NAPI from being scheduled on this context.
> + * Must be paired with napi_disable.
> + */
> static inline void napi_enable(struct napi_struct *n)
> {
It looks like small fix is needed here (I hope it would be faster
without my patch, thanks).
Jarek P.
prev parent reply other threads:[~2007-08-27 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 19:33 [PATCH] netdevice: kernel docbook addition Stephen Hemminger
2007-08-22 19:46 ` David Miller
2007-08-22 20:42 ` Randy Dunlap
2007-08-27 12:18 ` Jarek Poplawski [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=20070827121853.GA2854@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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 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.