From: Edward Cree <ecree@solarflare.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Michal Marek <mmarek@suse.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
Paul Bolle <pebolle@tiscali.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Triplett <josh@joshtriplett.org>, <netdev@vger.kernel.org>,
<linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/4] ptp_clock: allow for it to be optional
Date: Tue, 8 Nov 2016 13:10:26 +0000 [thread overview]
Message-ID: <cc41f1f3-1bc8-1835-1bf1-2d342768e49d@solarflare.com> (raw)
In-Reply-To: <1478556899-2951-4-git-send-email-nicolas.pitre@linaro.org>
On 07/11/16 22:14, Nicolas Pitre wrote:
> In order to break the hard dependency between the PTP clock subsystem and
> ethernet drivers capable of being clock providers, this patch provides
> simple PTP stub functions to allow linkage of those drivers into the
> kernel even when the PTP subsystem is configured out. Drivers must be
> ready to accept NULL from ptp_clock_register() in that case.
>
> And to make it possible for PTP to be configured out, the select statement
> in those driver's Kconfig menu entries is converted to the new "imply"
> statement. This way the PTP subsystem may have Kconfig dependencies of
> its own, such as POSIX_TIMERS, without having to make those ethernet
> drivers unavailable if POSIX timers are cconfigured out. And when support
> for POSIX timers is selected again then the default config option for PTP
> clock support will automatically be adjusted accordingly.
>
> The pch_gbe driver is a bit special as it relies on extra code in
> drivers/ptp/ptp_pch.c. Therefore we let the make process descend into
> drivers/ptp/ even if PTP_1588_CLOCK is unselected.
>
> Signed-off-by: Nicolas Pitre <nico@linaro.org>
> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
> Acked-by: Richard Cochran <richardcochran@gmail.com>
For the sfc change:
Acked-by: Edward Cree <ecree@solarflare.com>
And I accept that "suggests" isn't needed and the current "imply" semantics
are probably fine. If not we can always change it or resurrect "suggests".
next prev parent reply other threads:[~2016-11-08 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 22:14 [PATCH v3 0/4] make POSIX timers optional with some Kconfig help Nicolas Pitre
2016-11-07 22:14 ` [PATCH v3 1/4] kconfig: introduce the "imply" keyword Nicolas Pitre
2016-11-07 22:14 ` [PATCH v3 2/4] kconfig: regenerate *.c_shipped files after previous changes Nicolas Pitre
2016-11-07 22:31 ` Josh Triplett
2016-11-07 22:41 ` Nicolas Pitre
2016-11-07 23:12 ` Josh Triplett
2016-11-07 22:14 ` [PATCH v3 3/4] ptp_clock: allow for it to be optional Nicolas Pitre
2016-11-08 13:10 ` Edward Cree [this message]
2016-11-07 22:14 ` [PATCH v3 4/4] posix-timers: make it configurable Nicolas Pitre
2016-11-08 17:42 ` John Stultz
2016-11-08 18:19 ` Nicolas Pitre
2016-11-08 18:48 ` John Stultz
2016-11-07 22:31 ` [PATCH v3 0/4] make POSIX timers optional with some Kconfig help Nicolas Pitre
2016-11-08 16:47 ` Thomas Gleixner
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=cc41f1f3-1bc8-1835-1bf1-2d342768e49d@solarflare.com \
--to=ecree@solarflare.com \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=pebolle@tiscali.nl \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®