From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org, Ben Hutchings <bhutchings@solarflare.com>,
David Miller <davem@davemloft.net>,
Jacob Keller <jacob.e.keller@intel.com>,
John Stultz <john.stultz@linaro.org>,
Matthew Vick <matthew.vick@intel.com>
Subject: Re: [PATCH V3 net-next 3/4] ptp: link the phc device to its parent device
Date: Sat, 22 Sep 2012 10:32:41 -0700 [thread overview]
Message-ID: <1348335161.31385.11.camel@jtkirshe-mobl> (raw)
In-Reply-To: <5cbf85cdd74396119af11ba00b4b0bcd93f23ba0.1348332941.git.richardcochran@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
On Sat, 2012-09-22 at 19:02 +0200, Richard Cochran wrote:
> PTP Hardware Clock devices appear as class devices in sysfs. This
> patch
> changes the registration API to use the parent device, clarifying the
> clock's relationship to the underlying device.
>
> Signed-off-by: Richard Cochran <richardcochran@gmail.com>
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-22 17:32 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 [this message]
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 ` [PATCH V3 net-next 0/4] Two new PTP Hardware Clock features David Miller
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=1348335161.31385.11.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jacob.e.keller@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).