From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, aabdulla@nvidia.com, arjan@infradead.org,
manfred@colorfullife.com
Subject: Re: [PATCH] forcedeth: don't poll NV event 36
Date: Thu, 25 Dec 2008 18:08:00 -0800 (PST) [thread overview]
Message-ID: <20081225.180800.233126632.davem@davemloft.net> (raw)
In-Reply-To: <1229888646.3050.4.camel@johannes>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Sun, 21 Dec 2008 20:44:06 +0100
> Polling doesn't seem to be necessary on my hardware, at
> least I haven't seen any bad effects testing it a while.
> Remove the polling so the CPU doesn't have to wake up a
> hundred times per second.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Applied, thanks Johannes.
prev parent reply other threads:[~2008-12-26 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 19:44 [PATCH] forcedeth: don't poll NV event 36 Johannes Berg
2008-12-26 2:08 ` David 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=20081225.180800.233126632.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aabdulla@nvidia.com \
--cc=arjan@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=manfred@colorfullife.com \
--cc=netdev@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 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).