From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com,
alexander.h.duyck@intel.com, peter.p.waskiewicz.jr@intel.com,
john.ronciak@intel.com
Subject: Re: [PATCH 1/4] e1000e: save skb counts in TX to avoid cache misses
Date: Fri, 23 Apr 2010 23:30:52 -0700 (PDT) [thread overview]
Message-ID: <20100423.233052.226770500.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.00.1004231719050.16806@pokey.mtv.corp.google.com>
Intel folks, please integrate Tom's patches.
Tom, please always CC: the developers listed in MAINTAINERS
for the driver you are submitting patches to.
Thanks.
next prev parent reply other threads:[~2010-04-24 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 0:25 [PATCH 1/4] e1000e: save skb counts in TX to avoid cache misses Tom Herbert
2010-04-24 6:30 ` David Miller [this message]
2010-04-26 15:55 ` Alexander Duyck
2010-04-26 22:01 ` Jeff Kirsher
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=20100423.233052.226770500.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=therbert@google.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).