From: Heiko Carstens <hca@linux.ibm.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 Jun 17
Date: Thu, 18 Jun 2026 07:12:11 +0200 [thread overview]
Message-ID: <20260618051211.11310Bd9-hca@linux.ibm.com> (raw)
In-Reply-To: <ajK3HJdAhHJ85wYq@sirena.org.uk>
On Wed, Jun 17, 2026 at 04:02:52PM +0100, Mark Brown wrote:
> Hi all,
>
> The merge window is open, so please to not addd any v7.2 material
> to your linux-next included branches until after the merge window closes.
>
> Changes since 20260615:
>
> The origin tree acquired a build failure for which I applied a fixup.
>
> Non-merge commits (relative to Linus' tree): 6079
> 5884 files changed, 298566 insertions(+), 109672 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Any chance you forgot to push next-20260617 to git.kernel.org?
At least I can see only next-20260616, including the corresponding
master branch.
next prev parent reply other threads:[~2026-06-18 5:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 15:02 linux-next: Tree for Jun 17 Mark Brown
2026-06-18 5:12 ` Heiko Carstens [this message]
2026-06-18 11:18 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-06-17 6:21 Stephen Rothwell
2024-06-17 20:52 Mark Brown
2022-06-17 7:18 Stephen Rothwell
2021-06-17 10:19 Stephen Rothwell
2020-06-17 4:37 Stephen Rothwell
2019-06-17 9:33 Stephen Rothwell
2016-06-17 4:19 Stephen Rothwell
2015-06-17 3:26 Michael Ellerman
2014-06-17 3:00 Stephen Rothwell
2013-06-17 8:51 Stephen Rothwell
2013-06-17 10:04 ` Geert Uytterhoeven
2013-06-18 0:06 ` 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=20260618051211.11310Bd9-hca@linux.ibm.com \
--to=hca@linux.ibm.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