From: linas@austin.ibm.com (Linas Vepstas)
To: Ingo Oeser <netdev@axxeo.de>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
wenxiong@us.ibm.com, e1000-devel@lists.sourceforge.net,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
john.ronciak@intel.com, jeffrey.t.kirsher@intel.com,
Jeff Garzik <jeff@garzik.org>, NetDev <netdev@vger.kernel.org>,
"'Stephen Hemminger'" <shemminger@linux-foundation.org>
Subject: Re: [PATCH 2/2]: e1000: avoid lockup durig error recovery
Date: Fri, 9 Nov 2007 16:40:05 -0600 [thread overview]
Message-ID: <20071109224005.GQ4239@austin.ibm.com> (raw)
In-Reply-To: <200711091802.36365.netdev@axxeo.de>
On Fri, Nov 09, 2007 at 06:02:34PM +0100, Ingo Oeser wrote:
> Linas Vepstas schrieb:
> > + * napi_enabled_p - return non-zero if napi enabled
> > + *
> > + * Mnemonic: _p stands for "predicate", returning a yes/no
> > + * answer to the question.
>
> Call it "is_napi_enabled()" an nobody will ask :-)
Heh. The suffix _p is standard coding style for lisp/scheme
and first-order logic interpreters. This was my lame attempt
to introduce it to the kernel. I guess that lame duck won't fly.
--linas
next prev parent reply other threads:[~2007-11-09 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071107211935.GH4239@austin.ibm.com>
[not found] ` <20071107212404.GA15251@austin.ibm.com>
[not found] ` <47323319.10709@intel.com>
[not found] ` <20071107222446.GM4239@austin.ibm.com>
2007-11-07 22:45 ` [PATCH 2/2]: e1000: avoid lockup durig error recovery Kok, Auke
2007-11-07 23:21 ` Linas Vepstas
2007-11-09 17:02 ` Ingo Oeser
2007-11-09 22:40 ` Linas Vepstas [this message]
2007-11-10 16:55 ` Stephen Hemminger
2007-11-08 1:15 ` Stephen Hemminger
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=20071109224005.GQ4239@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@axxeo.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=wenxiong@us.ibm.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 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).