mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 9
Date: Mon, 9 Nov 2026 14:03:24 -0600	[thread overview]
Message-ID: <20261109200324.GA950470-robh@kernel.org> (raw)
In-Reply-To: <avHgrm2PmkCsLyDT@sirena.co.uk>

On Mon, Nov 09, 2026 at 03:03:10PM +0000, Mark Brown wrote:
> Hi all,
> 
> Changes since 20261105:
> 
> The exfat tree acquired a conflict with the origin tree.
> 
> The drivers-memory-fixes tree acquired a conflict with the origin tree.
> 
> The imx-mxs tree acquired a conflict with the origin tree.
> 
> The sound-asoc tree acquired multiple conflicts with the origin tree.
> 
> The mfd tree acquired multiple conflicts with the origin tree.
> 
> The spi tree acquired a conflict with the origin tree.
> 
> The gpio-brgl tree acquired multiple conflicts with the origin tree.
> 
> Non-merge commits (relative to Linus' tree): 2367
> 
> 
> ----------------------------------------------------------------------------
> 
> I have created today's linux-next tree at
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at https://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,
> an arm64 build of various kselftests, a KUnit build and run on arm64,
> 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 allyesconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
> sparc64 defconfig and htmldocs.
> 
> Below is a summary of the state of the merge.
> 
> I am currently merging 436 trees (counting Linus' and 135 trees of bug
> fix patches pending for the current release).

It looks like a number of trees are missing today. For example, clk, 
reset, and i2c trees have fixes, but not next branches.

Rob

  reply	other threads:[~2026-11-09 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 15:03 Mark Brown
2026-11-09 20:03 ` Rob Herring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-09  2:08 Stephen Rothwell
2022-11-09  5:37 Stephen Rothwell
2021-11-09  2:54 Stephen Rothwell
2021-11-09  2:55 ` Stephen Rothwell
2021-11-09  9:58   ` Geert Uytterhoeven
2021-11-09 11:00     ` Jan Kara
2020-11-09  7:17 Stephen Rothwell
2018-11-09  3:04 Stephen Rothwell
2017-11-09  6:42 Stephen Rothwell
2016-11-09  4:40 Stephen Rothwell
2015-11-09  3:06 Stephen Rothwell
2012-11-09  4:31 Stephen Rothwell
2011-11-09  2:58 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=20261109200324.GA950470-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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
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

all inboxes | Powered by JetHome®