From: Jeff Garzik <jgarzik@pobox.com>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: torvalds@osdl.org, stable@vger.kernel.org, auke@foo-projects.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
greg@kroah.com, jesse.brandeburg@intel.com,
john.ronciak@intel.com, linville@tuxdriver.org,
tony@mail.applog.com, bunk@stusta.de
Subject: Re: [PATCH] e1000: fix TX timout hang regression for 82542rev3
Date: Tue, 12 Sep 2006 11:46:51 -0400 [thread overview]
Message-ID: <4506D66B.7070202@pobox.com> (raw)
In-Reply-To: <20060911210021.972B41AB2A1@ahkok-mobl.jf.intel.com>
applied to #upstream-fixes
prev parent reply other threads:[~2006-09-12 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 21:00 [PATCH] e1000: fix TX timout hang regression for 82542rev3 Auke Kok
2006-09-12 15:46 ` Jeff Garzik [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=4506D66B.7070202@pobox.com \
--to=jgarzik@pobox.com \
--cc=auke-jan.h.kok@intel.com \
--cc=auke@foo-projects.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tony@mail.applog.com \
--cc=torvalds@osdl.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).