From: David Miller <davem@davemloft.net>
To: richardcochran@gmail.com
Cc: netdev@vger.kernel.org, bhutchings@solarflare.com,
jacob.e.keller@intel.com, jeffrey.t.kirsher@intel.com,
john.stultz@linaro.org, matthew.vick@intel.com
Subject: Re: [PATCH V3 net-next 0/4] Two new PTP Hardware Clock features
Date: Sat, 22 Sep 2012 15:43:34 -0400 (EDT) [thread overview]
Message-ID: <20120922.154334.1781240216569115874.davem@davemloft.net> (raw)
In-Reply-To: <cover.1348332940.git.richardcochran@gmail.com>
From: Richard Cochran <richardcochran@gmail.com>
Date: Sat, 22 Sep 2012 19:02:00 +0200
> This patch series adds two new features to the PHC code.
>
> * ChangeLog
> ** V3
> - Use the correct parent device in the solarflare driver.
> - Expand the sysfs documentation of clock_name.
> - Also document the clock_name field in the header file.
> ** V2
> - Preserves the clock_name attribute as it was meant to be, instead
> of making any changes to it.
> - Covers the registration API change in the brand new solarflare phc
> device, which was overlooked in V1.
>
> The first two patches let a user program find out the previously
> dialed frequency adjustment. This is primarily useful when restarting
> a PTP service, since without this information, the presumably correct
> adjustment will bias the new frequency estimation.
>
> The third patch links the phc class device to its parent device within
> the driver model and sysfs.
>
> The fourth patch adds a bit more documentation of the sysfs clock_name
> attribute. This should help clarify the naming scheme.
All applied, with a minor coding style correction made to patch #2
Thanks.
prev parent reply other threads:[~2012-09-22 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 17:02 [PATCH V3 net-next 0/4] Two new PTP Hardware Clock features Richard Cochran
2012-09-22 17:02 ` [PATCH V3 net-next 1/4] ptp: remember the adjusted frequency Richard Cochran
2012-09-22 17:02 ` [PATCH V3 net-next 2/4] ptp: provide the clock's " Richard Cochran
2012-09-22 17:02 ` [PATCH V3 net-next 3/4] ptp: link the phc device to its parent device Richard Cochran
2012-09-22 17:18 ` Ben Hutchings
2012-09-22 17:32 ` Jeff Kirsher
2012-09-22 17:02 ` [PATCH V3 net-next 4/4] ptp: clarify the clock_name sysfs attribute Richard Cochran
2012-09-22 17:20 ` Ben Hutchings
2012-09-22 19:43 ` 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=20120922.154334.1781240216569115874.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=jacob.e.keller@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.stultz@linaro.org \
--cc=matthew.vick@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/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).