From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arm-soc <arm@kernel.org>
Subject: Re: [GIT PULL 3/6] ARM: SoC driver updates for 5.1
Date: Wed, 6 Mar 2019 10:09:28 -0800 [thread overview]
Message-ID: <CAHk-=wgdJKaDt=Dp_DS+LL3bzRZUo2VHHMZU_VUMukSPzRJPUw@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a1-j-rr1MKnVqD8__YnqPsP8y4S_TWr+TRJScRvkrFymA@mail.gmail.com>
On Wed, Mar 6, 2019 at 7:34 AM Arnd Bergmann <arnd@arndb.de> wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-drivers
This caused a surprising number of kernel file rebuilds for me, and
the reason was
> include/linux/mod_devicetable.h | 9 +
It turns out that the above is indirectly included from a _lot_ of
code device header files.
The reason seems to be the various 'struct *_device_id' declarations,
that then all the different header files want.
So a tiny change in an oddball header file causes a lot of recompiles.
Oh well. I don't know if there is anything to be done, but I did react
to how some surprising changes cause a lot of build activity, and it's
not always obvious.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, arm-soc <arm@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 3/6] ARM: SoC driver updates for 5.1
Date: Wed, 6 Mar 2019 10:09:28 -0800 [thread overview]
Message-ID: <CAHk-=wgdJKaDt=Dp_DS+LL3bzRZUo2VHHMZU_VUMukSPzRJPUw@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a1-j-rr1MKnVqD8__YnqPsP8y4S_TWr+TRJScRvkrFymA@mail.gmail.com>
On Wed, Mar 6, 2019 at 7:34 AM Arnd Bergmann <arnd@arndb.de> wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-drivers
This caused a surprising number of kernel file rebuilds for me, and
the reason was
> include/linux/mod_devicetable.h | 9 +
It turns out that the above is indirectly included from a _lot_ of
code device header files.
The reason seems to be the various 'struct *_device_id' declarations,
that then all the different header files want.
So a tiny change in an oddball header file causes a lot of recompiles.
Oh well. I don't know if there is anything to be done, but I did react
to how some surprising changes cause a lot of build activity, and it's
not always obvious.
Linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-06 18:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 15:25 [GIT PULL 0/6] ARM: SoC changes for 5.1 Arnd Bergmann
2019-03-06 15:25 ` Arnd Bergmann
2019-03-06 15:33 ` [GIT PULL 2/6] ARM: SoC device tree updates " Arnd Bergmann
2019-03-06 15:33 ` Arnd Bergmann
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 15:34 ` [GIT PULL 3/6] ARM: SoC driver " Arnd Bergmann
2019-03-06 15:34 ` Arnd Bergmann
2019-03-06 18:09 ` Linus Torvalds [this message]
2019-03-06 18:09 ` Linus Torvalds
2019-03-06 18:15 ` Russell King - ARM Linux admin
2019-03-06 18:15 ` Russell King - ARM Linux admin
2019-03-06 18:28 ` Linus Torvalds
2019-03-06 18:28 ` Linus Torvalds
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 15:35 ` [GIT PULL 4/6] ARM: SoC defconfig " Arnd Bergmann
2019-03-06 15:35 ` Arnd Bergmann
2019-03-06 18:15 ` Linus Torvalds
2019-03-06 18:15 ` Linus Torvalds
2019-03-06 19:49 ` Arnd Bergmann
2019-03-06 19:49 ` Arnd Bergmann
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 15:36 ` [GIT PULL 5/6] ARM: New SoC family support " Arnd Bergmann
2019-03-06 15:36 ` Arnd Bergmann
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 15:38 ` [GIT PULL 6/6] ARM: SoC late updates " Arnd Bergmann
2019-03-06 15:38 ` Arnd Bergmann
2019-03-06 18:30 ` pr-tracker-bot
2019-03-06 18:30 ` pr-tracker-bot
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='CAHk-=wgdJKaDt=Dp_DS+LL3bzRZUo2VHHMZU_VUMukSPzRJPUw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.