From: Alan Cox <gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Romain Perier <romain.perier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: peter enderborg <peter.enderborg-7U/KSKJipcs@public.gmane.org>,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] time: Make NTP optionnal
Date: Mon, 20 Nov 2017 16:39:11 +0000 [thread overview]
Message-ID: <20171120163911.628daa14@alans-desktop> (raw)
In-Reply-To: <CABgxDoKXJSkx88XAN=pcL25GJtevM7wkEn4AbigZr1CYKrAWyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, 20 Nov 2017 17:29:53 +0100
Romain Perier <romain.perier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> So even if the correspondong syscall are disabled and the
> corresponding clocks too, you should return an -ENOSYS from the
> do_adjtimex helper, in case that another component tries to use it in
> the kernel, right ?
Probably - but you need to trace those callers and check.
Alan
prev parent reply other threads:[~2017-11-20 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 18:29 [PATCH] time: Make NTP optionnal Romain Perier
2017-11-20 13:52 ` Romain Perier
2017-11-20 14:10 ` peter enderborg
[not found] ` <dd52374f-af2d-3ff1-b9cf-fbf28634a739-7U/KSKJipcs@public.gmane.org>
2017-11-20 15:00 ` Romain Perier
[not found] ` <CABgxDoKm3PZuzV9H=jFnMOQoxKg2_byA7kane-kDhcVEwd9FJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-20 15:22 ` peter enderborg
2017-11-20 16:08 ` Alan Cox
2017-11-20 16:29 ` Romain Perier
[not found] ` <CABgxDoKXJSkx88XAN=pcL25GJtevM7wkEn4AbigZr1CYKrAWyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-20 16:39 ` Alan Cox [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=20171120163911.628daa14@alans-desktop \
--to=gnomes-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
--cc=john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter.enderborg-7U/KSKJipcs@public.gmane.org \
--cc=romain.perier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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