[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.20.1609131652230.14769@knanqh.ubzr>
Date: Tue, 13 Sep 2016 16:57:21 -0400 (EDT)
From: Nicolas Pitre <nicolas.pitre@...aro.org>
To: Thomas Gleixner <tglx@...utronix.de>
cc: John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [RFC/PATCH] posix-timers: make them configurable
On Fri, 9 Sep 2016, Thomas Gleixner wrote:
> On Thu, 8 Sep 2016, Nicolas Pitre wrote:
> > Small embedded systems typically don't need them. This removes about
> > 16KB from the kernel binary size on ARM when configured out.
> > Corresponding syscalls are routed to a stub logging the attempt to
> > use those syscalls which should be enough of a clue if they were
> > disabled without proper consideration.
> >
> > Signed-off-by: Nicolas Pitre <nico@...aro.org>
> >
> > diff --git a/drivers/ptp/Kconfig b/drivers/ptp/Kconfig
> > index ee3de3421f..00e6098e9a 100644
> > --- a/drivers/ptp/Kconfig
> > +++ b/drivers/ptp/Kconfig
> > @@ -6,7 +6,7 @@ menu "PTP clock support"
> >
> > config PTP_1588_CLOCK
> > tristate "PTP clock support"
> > - depends on NET
> > + depends on NET && POSIX_TIMERS
> > select PPS
> > select NET_PTP_CLASSIFY
> > help
>
> You forgot CONFIG_TIMERFD ....
Unless I'm mistaken, I don't see anything in timerfd.c that depends on
the (removed) POSIX timer code. What am I missing?
Nicolas
Powered by blists - more mailing lists