From: Richard Cochran <richardcochran@gmail.com>
To: "Brown, Aaron F" <aaron.f.brown@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net V4 0/2] igb: ptp hardware clock
Date: Sat, 28 Jan 2012 09:26:50 +0100 [thread overview]
Message-ID: <20120128082650.GA2275@netboy.at.omicron.at> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B2E07B8F1@ORSMSX101.amr.corp.intel.com>
On Fri, Jan 27, 2012 at 08:42:20PM +0000, Brown, Aaron F wrote:
> Yes, that does indeed resolve the compilation issue I was seeing in
> the lab, thanks... I'm assuming a set of .config files that were
> failing is no longer necessary.
Right, don't need them anymore.
Thanks,
Richard
prev parent reply other threads:[~2012-01-28 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 16:03 [PATCH net V4 0/2] igb: ptp hardware clock Richard Cochran
2012-01-21 16:03 ` [PATCH net V4 1/2] igb: add PTP Hardware Clock code Richard Cochran
2012-01-23 18:39 ` Keller, Jacob E
2012-01-24 17:44 ` Richard Cochran
2012-01-24 21:23 ` Keller, Jacob E
2012-01-27 19:25 ` Keller, Jacob E
2012-01-21 16:03 ` [PATCH net V4 2/2] igb: offer a PTP Hardware Clock instead of the timecompare method Richard Cochran
2012-01-23 3:57 ` [PATCH net V4 0/2] igb: ptp hardware clock Jeff Kirsher
2012-01-27 4:24 ` Jeff Kirsher
2012-01-27 10:11 ` Richard Cochran
2012-01-27 10:15 ` Jeff Kirsher
2012-01-27 10:22 ` Eric Dumazet
2012-01-27 10:56 ` Jeff Kirsher
2012-01-27 12:11 ` Richard Cochran
2012-01-27 20:42 ` Brown, Aaron F
2012-01-28 8:26 ` Richard Cochran [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=20120128082650.GA2275@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--cc=aaron.f.brown@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=eric.dumazet@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.ronciak@intel.com \
--cc=john.stultz@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).