From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
josh@joshtriplett.org, mingo@kernel.org, hpa@zytor.com,
richardcochran@gmail.com, pebolle@tiscali.nl,
ecree@solarflare.com, john.stultz@linaro.org, mmarek@suse.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/core] ptp_clock: Allow for it to be optional
Date: Fri, 18 Nov 2016 10:15:54 +0100 [thread overview]
Message-ID: <2998163.zQSyBK3yDq@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.20.1611171930580.22196@knanqh.ubzr>
On Thursday, November 17, 2016 7:48:00 PM CET Nicolas Pitre wrote:
> >
> > It was introduced in linux-next today, but it only happens if you
> > don't do a 'make clean' or 'make mrproper'. Apparently patch 1
> > of the series changes kconfig but that change does not trigger
> > a rebuild of the kconfig binary for me. After removing kconfig
> > from the object directory, it works again.
>
> That's odd. If I do a git checkout from linux-next of a commit before
> this series, then "make oldconfig", and then checkout of master and
> "make oldconfig again, in both cases I always get:
>
> $ make oldconfig
> HOSTCC scripts/kconfig/conf.o
> SHIPPED scripts/kconfig/zconf.tab.c
> SHIPPED scripts/kconfig/zconf.hash.c
> HOSTCC scripts/kconfig/zconf.tab.o
> HOSTLD scripts/kconfig/conf
> scripts/kconfig/conf --oldconfig Kconfig
> [...]
>
> And obviously no errors.
I usually build with "make -skj30", so it's possible that it only
happens in a parallel build environment on the first run.
> > I also ran into a problem with CONFIG_TIMERFD enabled but
> > CONFIG_POSIX_TIMERS turned off. This could be related to some
> > of my own patches though, haven't tried if that happens
> > with just your patches applied.
>
> Tried that combination in my checkout of linux-next, and once again no
> build errors here.
Ok, thanks for testing this. It must be something in the y2038
patches I have on top of next. They clashed quite a bit with your
work already, this added dependency is just one more detail for
me to remember with my series, nothing you need to worry about.
Arnd
next prev parent reply other threads:[~2016-11-18 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 5:10 [PATCH v4 0/6] make POSIX timers optional with some Kconfig help Nicolas Pitre
2016-11-11 5:10 ` [PATCH v4 1/6] kconfig: introduce the "imply" keyword Nicolas Pitre
2016-11-16 8:30 ` [tip:timers/core] Kconfig: Introduce " tip-bot for Nicolas Pitre
2016-11-11 5:10 ` [PATCH v4 2/6] kconfig: regenerate *.c_shipped files after previous changes Nicolas Pitre
2016-11-16 8:31 ` [tip:timers/core] Kconfig: Regenerate " tip-bot for Nicolas Pitre
2016-11-11 5:10 ` [PATCH v4 3/6] ptp_clock: allow for it to be optional Nicolas Pitre
2016-11-16 8:32 ` [tip:timers/core] ptp_clock: Allow " tip-bot for Nicolas Pitre
2016-11-17 16:44 ` Arnd Bergmann
2016-11-18 0:48 ` Nicolas Pitre
2016-11-18 9:15 ` Arnd Bergmann [this message]
2016-11-11 5:10 ` [PATCH v4 4/6] timer: move sys_alarm from timer.c to itimer.c Nicolas Pitre
2016-11-16 8:32 ` [tip:timers/core] timer: Move " tip-bot for Nicolas Pitre
2016-11-11 5:10 ` [PATCH v4 5/6] posix_cpu_timers_exit: wrong place to collect entropy Nicolas Pitre
2016-11-16 8:33 ` [tip:timers/core] posix_cpu_timers: Move the add_device_randomness() call to a proper place tip-bot for Nicolas Pitre
2016-11-11 5:10 ` [PATCH v4 6/6] posix-timers: make it configurable Nicolas Pitre
2016-11-16 0:48 ` John Stultz
2016-11-16 8:33 ` [tip:timers/core] posix-timers: Make them configurable tip-bot for Nicolas Pitre
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=2998163.zQSyBK3yDq@wuerfel \
--to=arnd@arndb.de \
--cc=ecree@solarflare.com \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.com \
--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®