To: Linux Next Mailing List <firstname.lastname@example.org>
Cc: Linux Kernel Mailing List <email@example.com>
Subject: linux-next: Tree for Apr 28
Date: Fri, 28 Apr 2023 16:22:49 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
This will most likely be my last release until Stephen gets back on 8th
May, it's *possible* there may be some releases next week since it being
the second half of the merge window means things run a bunch faster and
with less intervention but really don't rely on that.
Changes since 20230427:
The loongarch tree gained a conflict against the origin tree.
Non-merge commits (relative to Linus' tree): 3150
3568 files changed, 295586 insertions(+), 209942 deletions(-)
I have created today's linux-next tree at
(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
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 ppc64_defconfig
for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm
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,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
and pseries_le_defconfig and i386, arm64, s390, sparc and sparc64
defconfig and htmldocs. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).
Below is a summary of the state of the merge.
I am currently merging 358 trees (counting Linus' and 102 trees of bug
fix patches pending for the current merge release).
Stats about the size of the tree over time can be seen at
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
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
next reply other threads:[~2023-04-28 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 15:22 broonie [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-28 7:29 linux-next: Tree for Apr 28 Stephen Rothwell
2021-04-28 6:05 Stephen Rothwell
2020-04-28 8:10 Stephen Rothwell
2020-04-28 19:04 ` Nathan Chancellor
2020-04-29 1:24 ` Minchan Kim
2020-04-29 1:34 ` Nathan Chancellor
2020-04-29 1:54 ` Stephen Rothwell
2017-04-28 7:11 Stephen Rothwell
2016-04-28 6:11 Stephen Rothwell
2015-04-28 3:10 Stephen Rothwell
2014-04-28 6:57 Stephen Rothwell
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).