From: Richard Cochran <richardcochran@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Jeroen Van den Keybus <jeroen.vandenkeybus@triphase.com>,
bruce.w.allan@intel.com, e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net] e1000e: fix numeric overflow in phc settime method.
Date: Mon, 22 Apr 2013 19:56:04 +0200 [thread overview]
Message-ID: <20130422175604.GD2497@netboy> (raw)
In-Reply-To: <1366653202.2037.2.camel@jtkirshe-mobl>
On Mon, Apr 22, 2013 at 10:53:22AM -0700, Jeff Kirsher wrote:
>
> Thanks Richard, I will add this to my queue.
If it doesn't make it into 3.9, please submit this one to stable, too.
Thanks,
Richard
next prev parent reply other threads:[~2013-04-22 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 13:53 [PATCH net] e1000e: fix numeric overflow in phc settime method Richard Cochran
2013-04-22 17:53 ` Jeff Kirsher
2013-04-22 17:56 ` Richard Cochran [this message]
2013-04-22 18:17 ` Jeff Kirsher
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=20130422175604.GD2497@netboy \
--to=richardcochran@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jeroen.vandenkeybus@triphase.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).