From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, bruce.w.allan@intel.com
Subject: Re: [net-2.6 PATCH 1/6] e1000e: PHY loopback broken on 82578
Date: Fri, 03 Jul 2009 20:14:43 -0700 (PDT) [thread overview]
Message-ID: <20090703.201443.81204164.davem@davemloft.net> (raw)
In-Reply-To: <20090701232731.20555.63487.stgit@localhost.localdomain>
All 6 patches applied, thanks!
prev parent reply other threads:[~2009-07-04 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 23:27 [net-2.6 PATCH 1/6] e1000e: PHY loopback broken on 82578 Jeff Kirsher
2009-07-01 23:27 ` [net-2.6 PATCH 2/6] e1000e: delay after LCD reset and proper checks for PHY configuration done Jeff Kirsher
2009-07-01 23:28 ` [net-2.6 PATCH 3/6] e1000e: do not write SmartSpeed register bits on parts without support Jeff Kirsher
2009-07-01 23:28 ` [net-2.6 PATCH 4/6] e1000e: prevent NVM corruption on sectors larger than 4K Jeff Kirsher
2009-07-01 23:28 ` [net-2.6 PATCH 5/6] e1000e: delay second read of PHY_STATUS register on failure of first read Jeff Kirsher
2009-07-01 23:29 ` [net-2.6 PATCH 6/6] e1000e: disable K1 at 1000Mbps for 82577/82578 Jeff Kirsher
2009-07-04 3:14 ` 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=20090703.201443.81204164.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bruce.w.allan@intel.com \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@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).