From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 29
Date: Tue, 29 Jul 2025 15:42:49 +1000 [thread overview]
Message-ID: <20250729154249.0523ca98@canb.auug.org.au> (raw)
In-Reply-To: <20250729153510.3781ac91@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Hi all,
On Tue, 29 Jul 2025 15:35:10 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Changes since 20250728:
Please do not add any v6.18 material to your linux-next included
branches until after v6.17-rc1 has been released.
This tree has not received as much build testing as usual since I
currently do not have access to my build machine. Only one set of
builds have been done after all the trees were merged and the final
powerpc allyesconfig build has not been done since it takes so long.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-29 5:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 5:35 linux-next: Tree for Jul 29 Stephen Rothwell
2025-07-29 5:42 ` Stephen Rothwell [this message]
2025-07-29 8:32 ` linux-next: Tree for Jul 29 (BACKLIGHT_KTD2801) Randy Dunlap
2025-07-29 9:18 ` Duje Mihanović
2025-07-29 16:05 ` Randy Dunlap
2025-07-29 9:01 ` linux-next: Tree for Jul 29 (drivers/bluetooth/btintel_pcie.c) Randy Dunlap
2025-07-30 0:26 ` linux-next: Tree for Jul 29 (net/ipv4/netfilter/arp_tables.o) Randy Dunlap
2025-08-08 15:39 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2024-07-29 2:10 linux-next: Tree for Jul 29 Stephen Rothwell
2021-07-29 16:17 Mark Brown
2020-07-29 12:22 Stephen Rothwell
2019-07-29 4:58 Stephen Rothwell
2016-07-29 4:47 Stephen Rothwell
2015-07-29 7:47 Stephen Rothwell
2014-07-29 11:04 Stephen Rothwell
2013-07-29 6:39 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=20250729154249.0523ca98@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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