From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753177AbcKRJTL (ORCPT ); Fri, 18 Nov 2016 04:19:11 -0500 Received: from mout.kundenserver.de ([212.227.126.133]:65499 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752359AbcKRJTI (ORCPT ); Fri, 18 Nov 2016 04:19:08 -0500 From: Arnd Bergmann To: Nicolas Pitre 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 Message-ID: <2998163.zQSyBK3yDq@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: References: <1478841010-28605-4-git-send-email-nicolas.pitre@linaro.org> <22431516.ipZiDAzsn3@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:8itzFEaL58hBPbcG6lBWRes2WmYUaxUQbtlp03+MI5sx3Zzqnep rCDdY7FG2XjDNe/2p2uU6XeroVCHhxENfioSVkuMjl1khzrRYuK8DdTF/2hgZY77zkVXNHQ OCx820hWnpuAN92yzKWEqzkK7Crh0JEHRCaY06xW16q8BQ5QR39zwv59xzG6UY6QNjb5/yf 1krzuzg75pHML32r2X08A== X-UI-Out-Filterresults: notjunk:1;V01:K0:M/R2yCyCWj8=:yXjrSKYRz8MF7veoyxVQ2P U+Ww/xl04Syy/wQPcBiTmWRkF1DUXba4MvxirkBplNa40eFluVpR3YnPEERnw/xY8pURcyAJ1 mzipIxnjnxKy9VcM7FsUAjLOZB6BnYKF1004FIDqmpcMAJ/RUxwHoZbJL32PvUQvLwFJviM9F jgv7Yoc/tmLbDjxBvwgfBWbLmPsC7vuGSNzzh6sMbTAFYTFZVf1ESQp5BdlXFzyU8JXGsWVr9 qcq6XNMxl3O5nFN5osq62rU5ctB6QuRN9+E+G4Xjoj0Gfc8gOwrI1sIy4HUoH3xHuXSuAhOWk xNKxYb8nZLrPbJf+lICXdG3W6zRxILPhToKyx/WzY5GiFQcKhgQqfCxGsIHxdWGFGMQQMK17s cOvrScZ5BWRGmCl3zzXKyUNfcx15KXJmrI666yB7/1F/YRbc//Iu8dBKvmzrn0t8p1gXnuu7G W94MDj4ChODNoeqJ2tt+vqRdakyocoR6rnV4W1B89t0N7Ehg60IDdP5hJv0M9VlCUTarNBFxO RtZKTqzw05GbdJHHFgk4lhcGpZcIheMg8efFgTJg62sRFkyX51C3CQ3FqRcvrgryu5RLYezCL o6SuXRRhwmfwZtZw0YOkWxUKphPVGePWlXIUfPEE4qF0DKK9DyDYYY5kGhJiwbq2RoinUlvGe rfj3Bv40e12ZkTdvsXpybMit+ArwOHNXyIdeWd5nyXp9D4KRxGvbfK0s0Q5UnTnXYIXSCpKTm eLRPvRbnmHTrzLIu Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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