From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Masahiro Yamada <masahiroy@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: much more building going on
Date: Fri, 7 Jan 2022 17:13:19 +1100 [thread overview]
Message-ID: <20220107171319.0afa619a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
Hi all,
Since yesterday, my builds are taking much longer and it seems just
about everything is being rebuilt when there should be very little done.
One example is after mergeing the clockevents tree, the diffstat looks
like this:
$ git diff --stat HEAD^..
.../devicetree/bindings/timer/cdns,ttc.yaml | 3 +
.../bindings/timer/mstar,msc313e-timer.yaml | 46 ++++
.../devicetree/bindings/timer/nxp,tpm-timer.yaml | 6 +-
.../devicetree/bindings/timer/renesas,ostm.yaml | 20 +-
.../bindings/timer/rockchip,rk-timer.yaml | 1 -
MAINTAINERS | 1 +
drivers/clocksource/Kconfig | 12 +-
drivers/clocksource/Makefile | 1 +
drivers/clocksource/exynos_mct.c | 52 +++--
drivers/clocksource/renesas-ostm.c | 39 +++-
drivers/clocksource/timer-imx-sysctr.c | 6 +-
drivers/clocksource/timer-msc313e.c | 253 +++++++++++++++++++++
drivers/clocksource/timer-pistachio.c | 3 +-
13 files changed, 411 insertions(+), 32 deletions(-)
but my powerpc and arm builds rebuilt basically everything.
This happens for a lot of merges - though some do not rebuild very much
at all.
Any ideas about what changed yesterday? (I directed this to the kbuild
tree maintainer since the kbuild tree was updated yesterday - though
that may be a coincidence).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-01-07 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 6:13 Stephen Rothwell [this message]
2022-01-07 6:22 ` linux-next: much more building going on Stephen Rothwell
2022-01-08 6:14 ` Stephen Rothwell
2022-01-08 10:46 ` Masahiro Yamada
2022-01-08 11:22 ` Stephen Rothwell
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=20220107171319.0afa619a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=masahiroy@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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