LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: broonie@kernel.org
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org
Subject: linux-next: Tree for Feb 22
Date: Wed, 23 Feb 2022 01:41:35 +0000	[thread overview]
Message-ID: <20220223014135.2764641-1-broonie@kernel.org> (raw)

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.

             reply	other threads:[~2022-02-23  1:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  1:41 broonie [this message]
2022-02-23  6:05 ` linux-next: Tree for Feb 22 (NET_DSA_SMSC_LAN9303) Randy Dunlap
2022-02-23  6:08 ` linux-next: Tree for Feb 22 (NFSD_V2_ACL) Randy Dunlap
2022-02-23 15:58   ` Chuck Lever III
2022-02-24  6:45     ` Randy Dunlap
2022-02-24 15:08       ` Chuck Lever III
2022-02-24 16:37         ` Randy Dunlap
2022-02-24 16:45           ` Chuck Lever III
  -- strict thread matches above, loose matches on Subject: below --
2021-02-22  9:13 linux-next: Tree for Feb 22 Stephen Rothwell
2019-02-22  7:55 Stephen Rothwell
2018-02-22  3:37 Stephen Rothwell
2017-02-22  4:54 Stephen Rothwell
2016-02-22  7:03 Stephen Rothwell
2015-02-22  6:32 Stephen Rothwell
2013-02-22  4:28 Stephen Rothwell
2012-02-22  5:28 Stephen Rothwell
2008-02-22  6:04 Stephen Rothwell
2008-02-22  6:32 ` Frank Seidel
2008-02-22  6:58   ` Stephen Rothwell
2008-02-22  6:43 ` Frank Seidel
2008-02-22  7:04   ` Stephen Rothwell
2008-02-22  7:21 ` Stephen Rothwell
2008-02-22  7:25   ` Al Viro
2008-02-22  7:30     ` David Miller
2008-02-23  8:04       ` Andrew Morton
2008-02-22 22:12 ` Randy Dunlap

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=20220223014135.2764641-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --subject='Re: linux-next: Tree for Feb 22' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).