From: Richard Cochran <richardcochran@gmail.com>
To: Aleksey Makarov <aleksey.makarov@cavium.com>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Goutham,
Sunil" <Sunil.Goutham@cavium.com>,
Radoslaw Biernacki <rad@semihalf.com>,
Robert Richter <rric@kernel.org>,
David Daney <ddaney@caviumnetworks.com>
Subject: Re: [PATCH net-next v4 0/2] net: thunderx: add support for PTP clock
Date: Fri, 8 Dec 2017 07:45:40 -0800 [thread overview]
Message-ID: <20171208154540.ulmwofskhmwcczyd@localhost> (raw)
In-Reply-To: <20171208103442.19354-1-aleksey.makarov@cavium.com>
On Fri, Dec 08, 2017 at 01:34:38PM +0300, Aleksey Makarov wrote:
> This series adds support for IEEE 1588 Precision Time Protocol
> to Cavium ethernet driver.
>
> The first patch adds support for the Precision Time Protocol Clocks and
> Timestamping coprocessor (PTP) found on Cavium processors.
> It registers a new PTP clock in the PTP core and provides functions
> to use the counter in BGX, TNS, GTI, and NIC blocks.
>
> The second patch introduces support for the PTP protocol to the
> Cavium ThunderX ethernet driver.
>
> v4:
> - use IS_ENABLED. This fixes compilation of the ptp as a module (David Miller)
> - select PTP_1588_CLOCK, not depend on it. This fixes a build warning.
It should be "imply" not "select".
Thanks,
Richard
prev parent reply other threads:[~2017-12-08 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 10:34 [PATCH net-next v4 0/2] net: thunderx: add support for PTP clock Aleksey Makarov
2017-12-08 10:34 ` [PATCH net-next v4 1/2] net: add support for Cavium PTP coprocessor Aleksey Makarov
2017-12-08 13:43 ` Philippe Ombredanne
2017-12-08 10:34 ` [PATCH net-next v4 2/2] net: thunderx: add timestamping support Aleksey Makarov
2017-12-08 15:45 ` Richard Cochran [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=20171208154540.ulmwofskhmwcczyd@localhost \
--to=richardcochran@gmail.com \
--cc=Sunil.Goutham@cavium.com \
--cc=aleksey.makarov@cavium.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rad@semihalf.com \
--cc=rric@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).