From: David Miller <davem@davemloft.net>
To: auke-jan.h.kok@intel.com
Cc: netdev@vger.kernel.org, jesse.brandeburg@intel.com,
john.ronciak@intel.com
Subject: Re: [PATCH 7/7]: [NET]: Make ->poll() breakout consistent in Intel ethernet drivers.
Date: Tue, 08 Jan 2008 14:55:59 -0800 (PST) [thread overview]
Message-ID: <20080108.145559.77545176.davem@davemloft.net> (raw)
In-Reply-To: <4783C95B.8060005@intel.com>
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
Date: Tue, 08 Jan 2008 11:04:59 -0800
> this is exactly the change I was eyeballing and indeed this seems to be the
> general use case in most drivers anyway.
>
> I'll try to see how this impacts the (especially 4-port) TX performance issue with
> e1000e, but this should be just fine for now, and we can address later anyway.
>
> Acked-by: Auke Kok <auke-jan.h.kok@intel.com>
>
Ok, thanks for reviewing.
prev parent reply other threads:[~2008-01-08 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 5:41 [PATCH 7/7]: [NET]: Make ->poll() breakout consistent in Intel ethernet drivers David Miller
2008-01-08 19:04 ` Kok, Auke
2008-01-08 22:55 ` 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=20080108.145559.77545176.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.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).