From: Richard Cochran <richardcochran@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: kernel@pengutronix.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1] ptp: document struct ptp_clock_request members
Date: Wed, 18 Nov 2020 05:05:41 -0800 [thread overview]
Message-ID: <20201118130541.GD23320@hoboy.vegasvil.org> (raw)
In-Reply-To: <20201117213826.18235-1-a.fatoum@pengutronix.de>
On Tue, Nov 17, 2020 at 10:38:26PM +0100, Ahmad Fatoum wrote:
> It's arguable most people interested in configuring a PPS signal
> want it as external output, not as kernel input. PTP_CLK_REQ_PPS
> is for input though. Add documentation to nudge readers into
> the correct direction.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Thanks!
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2020-11-18 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 21:38 [PATCH net-next v1] ptp: document struct ptp_clock_request members Ahmad Fatoum
2020-11-18 13:05 ` Richard Cochran [this message]
2020-11-18 18:51 ` Jakub Kicinski
2020-11-18 21:35 ` Jacob Keller
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=20201118130541.GD23320@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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).