From: Richard Cochran <richardcochran@gmail.com>
To: Frank Li <Frank.Li@freescale.com>
Cc: lznuaa@gmail.com, shawn.guo@linaro.org, davem@davemloft.net,
linux-arm-kernel@lists.infradead.or, netdev@vger.kernel.org,
s.hauer@pengutronix.de
Subject: Re: [PATCH 1/1] net: fec: report correct hardware stamping info to ethtool
Date: Sun, 6 Jan 2013 09:20:24 +0100 [thread overview]
Message-ID: <20130106082023.GC2276@netboy.at.omicron.at> (raw)
In-Reply-To: <1357436318-12425-1-git-send-email-Frank.Li@freescale.com>
Frank,
You have a bad email address as one of the recipients:
linux-arm-kernel@lists.infradead.or
***
You also did that last time. Please take care and fix it.
Thanks,
Richard
next prev parent reply other threads:[~2013-01-06 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 1:38 [PATCH 1/1] net: fec: report correct hardware stamping info to ethtool Frank Li
2013-01-06 8:09 ` Richard Cochran
2013-01-06 8:15 ` Richard Cochran
2013-01-06 8:20 ` Richard Cochran [this message]
2013-01-06 8:23 ` Frank Li
2013-01-06 11:33 ` Sascha Hauer
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=20130106082023.GC2276@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--cc=Frank.Li@freescale.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.or \
--cc=lznuaa@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.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).