From: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alexander Gordeev <lasaine@lvk.cs.msu.su>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH][RESEND] pps: kc: fix non-tickless system config dependency
Date: Wed, 21 Sep 2016 18:38:01 +0200 [thread overview]
Message-ID: <57E2B769.50202@maciej.szmigiero.name> (raw)
CONFIG_NO_HZ currently only sets the default value
of dynticks config so if PPS kernel consumer needs
periodic timer ticks it should depend on
!CONFIG_NO_HZ_COMMON instead of !CONFIG_NO_HZ.
Otherwise it is possible to enable it even on
tickless system which has CONFIG_NO_HZ not set and
CONFIG_NO_HZ_IDLE (or CONFIG_NO_HZ_FULL) set.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
---
This is a resend without functional changes since previous
submission and resubmission weren't picked up.
@Rodolfo: Could you ack this, please?
drivers/pps/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pps/Kconfig b/drivers/pps/Kconfig
index 7512e98e9311..564a51abeece 100644
--- a/drivers/pps/Kconfig
+++ b/drivers/pps/Kconfig
@@ -31,7 +31,7 @@ config PPS_DEBUG
config NTP_PPS
bool "PPS kernel consumer support"
- depends on !NO_HZ
+ depends on !NO_HZ_COMMON
help
This option adds support for direct in-kernel time
synchronization using an external PPS signal.
next reply other threads:[~2016-09-21 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 16:38 Maciej S. Szmigiero [this message]
2016-09-21 16:54 ` [PATCH][RESEND] pps: kc: fix non-tickless system config dependency Rodolfo Giometti
-- strict thread matches above, loose matches on Subject: below --
2016-07-02 20:30 Maciej S. Szmigiero
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=57E2B769.50202@maciej.szmigiero.name \
--to=mail@maciej.szmigiero.name \
--cc=akpm@linux-foundation.org \
--cc=giometti@enneenne.com \
--cc=lasaine@lvk.cs.msu.su \
--cc=linux-kernel@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).