From: David Miller <davem@davemloft.net>
To: pcnet32@verizon.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 5/7]: [NET]: Fix drivers to handle napi_disable() disabling interrupts.
Date: Tue, 08 Jan 2008 22:44:58 -0800 (PST) [thread overview]
Message-ID: <20080108.224458.203158908.davem@davemloft.net> (raw)
In-Reply-To: <1199859269.9002.6.camel@Linux.home>
From: Don Fry <pcnet32@verizon.net>
Date: Tue, 08 Jan 2008 22:14:29 -0800
> Tested pcnet32 on x86_64 box and see no problems with the change.
> The code is only exercised if doing loopback testing, or changing
> the ring size during a receive storm.
>
> Acked-by: Don Fry <pcnet32@verizon.net>
Thanks for testing and the feedback.
next prev parent reply other threads:[~2008-01-09 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 6:14 [PATCH 5/7]: [NET]: Fix drivers to handle napi_disable() disabling interrupts Don Fry
2008-01-09 6:44 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-08 5:40 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=20080108.224458.203158908.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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).