From: Andy Shevchenko <andriy.shevchenko@intel.com>
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 Feb 25
Date: Wed, 25 Feb 2026 19:38:42 +0100 [thread overview]
Message-ID: <aZ9BsrhtNZ5LlFAc@black.igk.intel.com> (raw)
In-Reply-To: <aZ8pWvKqd9DhNYRD@sirena.org.uk>
On Wed, Feb 25, 2026 at 04:54:50PM +0000, Mark Brown wrote:
> Hi all,
>
> Changes since 20260224:
>
> The URL for the imx-mxs tree was updated.
>
> The socfpga tree was added.
>
> The ntfs tree was added.
>
> The drm-msm-fixes tree acquired a conflict with the origin tree.
>
> The net-next tree acquired a conflict with the net tree.
>
> The bluetooth tree acquired a conflict with the net tree.
>
> The drm-misc lost it's build failure.
>
> The staging tree acquired a conflict with the staging.current tree.
>
> Non-merge commits (relative to Linus' tree): 1890
> 2114 files changed, 196952 insertions(+), 29041 deletions(-)
spi/for-next doesn't include spi/for-7.1. So SPI changes missed Linux Next for
a few days already. Not sure about other your repositories.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-25 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 16:54 linux-next: Tree for Feb 25 Mark Brown
2026-02-25 18:38 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-25 6:09 Stephen Rothwell
2023-02-25 3:32 Stephen Rothwell
2022-02-26 1:45 broonie
2021-02-25 4:43 Stephen Rothwell
2020-02-25 3:24 Stephen Rothwell
2019-02-25 7:35 Stephen Rothwell
2016-02-25 5:17 Stephen Rothwell
2015-02-25 3:51 Stephen Rothwell
2014-02-25 7:48 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=aZ9BsrhtNZ5LlFAc@black.igk.intel.com \
--to=andriy.shevchenko@intel.com \
--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