From: Richard Cochran <richardcochran@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
bruce.w.allan@intel.com, Jacob Keller <jacob.e.keller@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Matthew Vick <matthew.vick@intel.com>
Subject: Re: [PATCH net-next 0/4] igb: auxiliary PHC functions for the i210.
Date: Wed, 19 Nov 2014 07:31:03 +0100 [thread overview]
Message-ID: <20141119063103.GA4109@localhost.localdomain> (raw)
In-Reply-To: <1416266118.2983.3.camel@jtkirshe-mobl.jf.intel.com>
On Mon, Nov 17, 2014 at 03:15:18PM -0800, Jeff Kirsher wrote:
> Thanks Richard, I have added your series of igb patches to my queue.
Jeff, please hold off on these. I found a bug in the PPS code. I will
re-submit with a fix.
Thanks,
Richard
next prev parent reply other threads:[~2014-11-19 6:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 23:06 [PATCH net-next 0/4] igb: auxiliary PHC functions for the i210 Richard Cochran
2014-11-17 23:06 ` [PATCH net-next 1/4] igb: refactor time sync interrupt handling Richard Cochran
2014-11-17 23:06 ` [PATCH net-next 2/4] igb: do not clobber the TSAUXC bits on reset Richard Cochran
2014-11-17 23:22 ` Keller, Jacob E
2014-11-17 23:06 ` [PATCH net-next 3/4] igb: enable internal PPS for the i210 Richard Cochran
2014-11-17 23:24 ` Keller, Jacob E
2014-11-19 6:37 ` Richard Cochran
2014-11-19 19:32 ` Keller, Jacob E
2014-11-19 20:26 ` Richard Cochran
2014-11-19 21:06 ` Keller, Jacob E
2014-11-20 9:18 ` Richard Cochran
2014-11-20 21:28 ` Keller, Jacob E
2014-11-21 5:49 ` Richard Cochran
2014-11-17 23:06 ` [PATCH net-next 4/4] igb: enable auxiliary PHC functions " Richard Cochran
2014-11-17 23:28 ` Keller, Jacob E
2014-11-17 23:15 ` [PATCH net-next 0/4] igb: " Jeff Kirsher
2014-11-19 6:31 ` Richard Cochran [this message]
2014-11-19 8:43 ` Jeff Kirsher
-- strict thread matches above, loose matches on Subject: below --
2013-05-27 9:21 Richard Cochran
2013-05-28 15:58 ` Vick, Matthew
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=20141119063103.GA4109@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=jacob.e.keller@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.ronciak@intel.com \
--cc=matthew.vick@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.