* linux-next: Tree for May 8
@ 2026-05-08 13:30 Thierry Reding
2026-05-10 1:30 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Thierry Reding @ 2026-05-08 13:30 UTC (permalink / raw)
To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List
Hi all,
I will be on holiday for a week starting Monday, and I don't plan on
creating a linux-next tree during that time.
Changes since 20260507:
The cix tree acquired a conflict with the arm-soc tree.
The stm32 tree acquired a conflict with the arm-soc tree.
The hwmon-staging tree acquired a conflict with the hwmon-fixes tree.
Non-merge commits (relative to Linus' tree): 3529
4221 files changed, 239791 insertions(+), 83377 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
and a native build of tools/perf. After the final fixups (if any), I do
an x86_64 modules_install followed by builds for x86_64 allnoconfig,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 422 trees (counting Linus' and 129 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Paul Gortmaker for triage and bug fixes.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: Tree for May 8
2026-05-08 13:30 linux-next: Tree for May 8 Thierry Reding
@ 2026-05-10 1:30 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2026-05-10 1:30 UTC (permalink / raw)
To: Thierry Reding; +Cc: Linux Next Mailing List, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
On Fri, May 08, 2026 at 03:30:20PM +0200, Thierry Reding wrote:
> I will be on holiday for a week starting Monday, and I don't plan on
> creating a linux-next tree during that time.
Thanks for stepping up here! I will also continue to be on holiday next
week so it is unlikely there will be any -next releases until 18th May.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-05-10 1:30 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-08 13:30 linux-next: Tree for May 8 Thierry Reding
2026-05-10 1:30 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox