From: Mark Brown <broonie@kernel•org>
To: Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: Tree for Jun 20
Date: Thu, 20 Jun 2024 17:10:20 +0100 [thread overview]
Message-ID: <ZnRUbK1pvBJqOsoh@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
Hi all,
Changes since 20240619:
The v4l-dvb-next tree gained a build failure, I used the version from
20240619 instead.
The memblock tree gained a conflict with Linus' tree.
Non-merge commits (relative to Linus' tree): 6610
6991 files changed, 595079 insertions(+), 119966 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
and a native build of tools/perf.
Below is a summary of the state of the merge.
I am currently merging 377 trees (counting Linus' and 106 trees of bug
fix patches pending for the current merge release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-06-20 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 16:10 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-20 12:13 linux-next: Tree for Jun 20 Stephen Rothwell
2023-06-20 5:26 Stephen Rothwell
2022-06-20 8:42 Stephen Rothwell
2019-06-20 10:46 Stephen Rothwell
2018-06-20 4:42 Stephen Rothwell
2017-06-20 6:00 Stephen Rothwell
2016-06-20 6:05 Stephen Rothwell
2016-06-20 21:59 ` Sudip Mukherjee
2015-06-20 14:54 Stephen Rothwell
2014-06-20 5:36 Stephen Rothwell
2013-06-20 8:26 Stephen Rothwell
2012-06-20 7:35 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=ZnRUbK1pvBJqOsoh@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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