From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM.
Date: Wed, 28 Dec 2016 09:15:25 +0100 [thread overview]
Message-ID: <20161228081524.GA3826@netboy> (raw)
In-Reply-To: <1481720175-12703-1-git-send-email-andrei.pistirica@microchip.com>
On Wed, Dec 14, 2016 at 02:56:14PM +0200, Andrei Pistirica wrote:
> Note 1: Kbuild uses "select" instead of "imply", and the macb maintainer agreed
> to make the change when it will be available in net-next.
> +config MACB_USE_HWSTAMP
> + bool "Use IEEE 1588 hwstamp"
> + depends on MACB
> + default y
> + select PTP_1588_CLOCK
The imply key word has been merged as of:
237e3ad Kconfig: Introduce the "imply" keyword
Please use it.
Thanks,
Richard
> + ---help---
> + Enable IEEE 1588 Precision Time Protocol (PTP) support for MACB.
next prev parent reply other threads:[~2016-12-28 8:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 12:56 [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM Andrei Pistirica
2016-12-14 12:56 ` [RFC PATCH net-next v4 2/2] macb: Enable 1588 support in SAMA5Dx platforms Andrei Pistirica
2016-12-20 16:38 ` Rafal Ozieblo
2016-12-28 8:15 ` Richard Cochran [this message]
2016-12-28 13:23 ` [RFC PATCH net-next v4 1/2] macb: Add 1588 support in Cadence GEM Rafal Ozieblo
2017-01-02 9:36 ` Rafal Ozieblo
2017-01-02 11:31 ` Richard Cochran
2017-01-02 11:43 ` Harini Katakam
2017-01-02 16:03 ` Richard Cochran
2017-01-02 14:47 ` Nicolas Ferre
2017-01-02 16:13 ` Richard Cochran
2017-01-03 5:06 ` Harini Katakam
2017-01-03 10:20 ` Richard Cochran
2017-01-03 10:29 ` Richard Cochran
2017-01-03 10:48 ` Harini Katakam
2017-01-03 10:47 ` Rafal Ozieblo
2017-01-03 11:14 ` Richard Cochran
2017-01-11 14:34 ` Andrei.Pistirica at microchip.com
2017-01-03 14:22 ` Nicolas Ferre
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=20161228081524.GA3826@netboy \
--to=richardcochran@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).