From: Stephen Rothwell <sfr@canb.auug.org.au>
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 17
Date: Mon, 28 Feb 2022 09:33:20 +1100 [thread overview]
Message-ID: <20220228093320.7ac8e394@canb.auug.org.au> (raw)
In-Reply-To: <Yg+hpgB4EOp9DNOA@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
Hi Mark,
On Fri, 18 Feb 2022 13:39:50 +0000 Mark Brown <broonie@kernel.org> wrote:
>
> On Thu, Feb 17, 2022 at 08:51:33PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > News: there will be no linux-next releases from Friday Feb 18 until
> > Friday Feb 25 inclusive.
>
> I'll try to provide cover from Monday as usual, I'm on holiday myself
> today so not likely to be anything today.
Thanks again for stepping up unasked.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-27 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 9:51 linux-next: Tree for Feb 17 Stephen Rothwell
2022-02-18 13:39 ` Mark Brown
2022-02-27 22:33 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 4:03 Stephen Rothwell
2021-02-17 12:42 Stephen Rothwell
2020-02-17 4:18 Stephen Rothwell
2017-02-17 5:49 Stephen Rothwell
2016-02-17 5:39 Stephen Rothwell
2016-02-17 11:52 ` Sudip Mukherjee
2016-02-17 17:37 ` David Daney
2016-02-23 12:51 ` Sudip Mukherjee
2015-02-17 5:02 Stephen Rothwell
2014-02-17 6:23 Stephen Rothwell
2012-02-17 5:50 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=20220228093320.7ac8e394@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).