From: Stephen Rothwell <sfr@canb•auug.org.au>
To: unlisted-recipients:; (no To-header on input)
Cc: broonie@kernel•org,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Sep 30
Date: Mon, 3 Oct 2022 15:47:46 +1100 [thread overview]
Message-ID: <20221003154746.1cf5cbea@canb.auug.org.au> (raw)
In-Reply-To: <20220930154710.548289-1-broonie@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
Hi all,
On Fri, 30 Sep 2022 16:47:10 +0100 broonie@kernel•org wrote:
>
> Stephen should be back on Monday and normal service resumed.
Normal service will resume tomorrow (as today is a public holiday here)
so there will be no linux-next release today.
I would like to publicly thank Mark for taking up the burden of
linux-next again.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-03 4:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 15:47 linux-next: Tree for Sep 30 broonie
2022-10-01 21:25 ` linux-next: Tree for Sep 30 (i386 non-SMP non-APIC w/ IRQ_DOMAIN: build errors) Randy Dunlap
2022-10-03 18:26 ` Marc Zyngier
2022-10-03 21:19 ` Borislav Petkov
2022-10-03 4:47 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-30 3:54 linux-next: Tree for Sep 30 Stephen Rothwell
2021-09-30 7:16 Stephen Rothwell
2020-09-30 12:11 Stephen Rothwell
2019-09-30 3:44 Stephen Rothwell
2016-09-30 8:14 Stephen Rothwell
2015-09-30 6:12 Stephen Rothwell
2015-09-30 8:11 ` Sudip Mukherjee
2015-09-30 12:54 ` Geert Uytterhoeven
2015-09-30 13:31 ` Sudip Mukherjee
2014-09-30 10:12 Stephen Rothwell
2014-09-30 16:26 ` Guenter Roeck
2013-09-30 10:20 Thierry Reding
2013-10-12 20:30 ` 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=20221003154746.1cf5cbea@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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