Geert Uytterhoeven @geert@society.oftrolls.com

Does insulting the Swedish help their case? https://dsocdn.akamaized.net/Assets/Images_Upload/2019/10/05/brexitschotland.jpg?

Summarized: during the v5.4 merge window, an atari_defconfig kernel has shrunk by 60 KiB, (compared to v5.3). Note that without commit ac7c3e4ff401b304 ("compiler: enable CONFIG_OPTIMIZE_INLINING forcibly"), kernel size would have grown by 42 KiB, which is inline (no pun intended) with the trend in previous merge windows.

Eleventh day of the v5.4 merge window, and an atari_defconfig kernel has shrunk by 102 KiB, (compared to yesterday), thanks to commit ac7c3e4ff401b304 ("compiler: enable
CONFIG_OPTIMIZE_INLINING forcibly").

Tenth day of the v5.4 merge window, and an atari_defconfig kernel has shrunk by 130 bytes (compared to yesterday).

More advancements in the v5.4 merge window: an atari_defconfig kernel has grown by another 22 KiB, with the lion's share due to the growth of struct kernel_symbol.

Never too late to learn that Paris Subway Line 4 runs Linux/m68k. #er2019-dinner-track

Does it match? #er2019 https://embedded-recipes.org/2019/talks/herd-your-socs-become-a-matchmaker/

Fourth day of the v5.4 merge window, and an atari_defconfig kernel has grown by ca. 2.5 KiB (in addition to the growth on the days before)...

And talking about run-time memory consumption:

+DMA: preallocated 256 KiB pool for atomic allocations

Third day of the v5.4 merge window, and an atari_defconfig kernel has grown by ca. 14 KiB (in addition to the growth on the days before)...

Second day of the v5.4 merge window, and an atari_defconfig kernel has grown by ca. 2 KiB (in addition to the growth on Day 1)...

First day of the v5.4 merge window, and an atari_defconfig kernel has already grown by ca. 1 KiB...

Looking forward to meet Dilbert at OSS+ELC-E!
https://dilbert.com/strip/2019-09-05
https://osseu19.sched.com/event/TPD1/women-in-open-source-lunch-pre-registration-required

https://lore.kernel.org/linux-next/20190905160237.2e972a89@canb.auug.org.au/ So please refrain from breaking anything before the release of v5.4-rc1.
Thanks for your cooperation! ;-)