Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   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 Feb 23
Date:   Thu, 24 Feb 2022 01:44:40 +0000
Message-Id: <20220224014440.1397777-1-broonie@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi all,

Note that today's -next again does not include the akpm tree since it's
been a long day and the conflicts especially with the mm code seemed
more than it was wise for me to attempt.  I'll have another go tomorrow
but no guarantees, I got further today.

Changes since 20220222:

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

The drm-tegra tree gained a conflict with the drm tree.

The mfd tree gained a build failure, I used the version from yesterday
instead.

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

The nvmem tree gained a conflict with the spi tree.

The nvmem tree gained a conflict with the char-misc tree.

I applied a fix for the build failure in the maple tree so merged
today's version.

The folio tree gained several conflicts with the maple tree.

Non-merge commits (relative to Linus' tree): 7020
 7614 files changed, 874525 insertions(+), 213969 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.