From: "Arnd Bergmann" <arnd@arndb.de>
To: "Johan Hovold" <johan@kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
"linux-csky@vger.kernel.org" <linux-csky@vger.kernel.org>,
linux-hexagon@vger.kernel.org, loongarch@lists.linux.dev,
"linux-openrisc@vger.kernel.org" <linux-openrisc@vger.kernel.org>,
linux-snps-arc@lists.infradead.org
Subject: Re: [GIT PULL] asm-generic updates for 6.11
Date: Wed, 17 Jul 2024 10:01:10 +0200 [thread overview]
Message-ID: <be80d8f6-2a1b-4f63-a43e-652fa5328d11@app.fastmail.com> (raw)
In-Reply-To: <ZpdnhhaQum_epcGp@hovoldconsulting.com>
On Wed, Jul 17, 2024, at 08:41, Johan Hovold wrote:
> On Wed, Jul 17, 2024 at 08:01:43AM +0200, Arnd Bergmann wrote:
>> On Wed, Jul 17, 2024, at 07:08, Linus Torvalds wrote:
>> > On Tue, 16 Jul 2024 at 21:57, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>> >>
>> >> Note, it really might be just 'allmodconfig'. We've had things that
>> >> depend on config entries in the past, eg the whole
>> >> CONFIG_HEADERS_INSTALL etc could affect things.
>>
>> I had tried a partial allmodconfig build earlier to save time,
>> did a full build again now, still nothing:
>
> FWIW, I noticed this last Friday as well when I did a few builds of
> linux-next and every change I made triggered what appeared to be a full
> rebuild of the tree.
>
> This was with a trimmed config [1] and separate build tree (tmpfs).
Thanks, that makes it quicker to try out. I'm now using
your config to do more testing. I still don't see it with
a normal build though.
I do see that setting the timestamp of syscall.tbl to
a future date does result in always rebuilding everything,
but I don't think that is what you are seeing, since that
also produces a warning from make:
arnd@studio:~/arm-soc/build/bisect$ touch -t 202501010000 arch/x86/entry/syscalls/syscall_64.tbl
arnd@studio:~/arm-soc/build/bisect$ make ARCH=x86 CROSS_COMPILE=x86_64-linux-
make[2]: Warning: File 'arch/x86/entry/syscalls/syscall_64.tbl' has modification time 14483017 s in the future
SYSHDR arch/x86/include/generated/uapi/asm/unistd_64.h
SYSHDR arch/x86/include/generated/uapi/asm/unistd_x32.h
SYSHDR arch/x86/include/generated/asm/unistd_64_x32.h
SYSTBL arch/x86/include/generated/asm/syscalls_64.h
make[2]: warning: Clock skew detected. Your build may be incomplete.
Arnd
next prev parent reply other threads:[~2024-07-17 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 21:14 [GIT PULL] asm-generic updates for 6.11 Arnd Bergmann
2024-07-16 19:25 ` pr-tracker-bot
2024-07-17 4:02 ` Linus Torvalds
2024-07-17 4:43 ` Arnd Bergmann
2024-07-17 4:57 ` Linus Torvalds
2024-07-17 5:08 ` Linus Torvalds
2024-07-17 6:01 ` Arnd Bergmann
2024-07-17 6:41 ` Johan Hovold
2024-07-17 8:01 ` Arnd Bergmann [this message]
2024-07-17 8:17 ` Johan Hovold
2024-07-17 9:36 ` Arnd Bergmann
2024-07-17 10:54 ` Arnd Bergmann
2024-07-17 12:45 ` Arnd Bergmann
2024-07-17 7:18 ` Arnd Bergmann
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=be80d8f6-2a1b-4f63-a43e-652fa5328d11@app.fastmail.com \
--to=arnd@arndb.de \
--cc=johan@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=torvalds@linux-foundation.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