linux-kernel - linux-next: Tree for Feb 22

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220223014135.2764641-1-broonie@kernel.org>
Date:   Wed, 23 Feb 2022 01:41:35 +0000
From:   broonie@...nel.org
To:     Linux Next Mailing List <linux-next@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        akpm@...ux-foundation.org
Subject: linux-next: Tree for Feb 22

Hi all,

Note that today's -next does not include the akpm tree since it's been a
long day and the conflicts seemed more than it was wise for me to
attempt at this point.  I'll have another go tomorrow but no guarantees.

Changes since 20220217:

The mips tree gained a conflict with the asm-generic tree.

The nds32 tree gained a conflict with the kbuild tree.

The drm tree gained a conflict with the drm-intel-fixes tree.

The modules tree gained a build failure, I used the version from
20220217.

The kvm tree gained a conflict with the kvm-fixes tree.

The iio tree gained a conflcit with the char-misc.current tree.

The sysctl tree gained a conflict with the tip tree.

The maple tree gained a conflict against the parisc tree.

The maple tree gained a conflict against the memblock tree.

The maple tree gained a build failure so I used the version from
20220217.

The akpm tree was dropped.

Non-merge commits (relative to Linus' tree): 6779
 7408 files changed, 823378 insertions(+), 211667 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 are also quilt-import.log and merge.log
files 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. After the
final fixups (if any), I do an x86_64 modules_install followed by builds
for x86_64 allnoconfig, arm64 allnoconfig, arm64 allyesconfig and i386,
and arm64 and htmldocs.

Below is a summary of the state of the merge.

I am currently merging 346 trees (counting Linus' and 93 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.