From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, bphilips@novell.com,
stable@kernel.org, bruce.w.allan@intel.com
Subject: Re: [net-2.6 PATCH] e1000e: 82577/82578 PHY register access issues
Date: Mon, 02 Aug 2010 21:10:22 -0700 (PDT) [thread overview]
Message-ID: <20100802.211022.124002477.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTi=P_+3wpmAA5+eqaWoGE39OkZPFhRXEuXGypAco@mail.gmail.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Mon, 2 Aug 2010 18:04:43 -0700
> Have you sync'd up your net-next-2.6 tree with net-2.6 tree? Because
> I do not see this change in the net-next-2.6 tree.
No, I plan to do that tonight or tomorrow.
prev parent reply other threads:[~2010-08-03 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 22:28 [net-2.6 PATCH] e1000e: 82577/82578 PHY register access issues Jeff Kirsher
2010-07-28 4:06 ` David Miller
2010-08-03 1:04 ` Jeff Kirsher
2010-08-03 4:10 ` 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=20100802.211022.124002477.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bphilips@novell.com \
--cc=bruce.w.allan@intel.com \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).