All of lore.kernel.org
 help / color / mirror / Atom feed
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 Dec 8
Date: Fri, 10 Dec 2021 09:07:16 +1100	[thread overview]
Message-ID: <20211210090716.6a991c08@canb.auug.org.au> (raw)
In-Reply-To: <YbH3lT7fh+YCCwjx@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

Hi Mark,

On Thu, 9 Dec 2021 12:33:25 +0000 Mark Brown <broonie@kernel.org> wrote:
>
> On Wed, Dec 08, 2021 at 06:38:14PM +1100, Stephen Rothwell wrote:
> 
> > News: I will (probably) do no linux-next releases between Dec 9 and Dec
> > 19, inclusive.  
> 
> I'll try to start provide some cover for this, probably starting
> tomorrow unless a build for today runs *very* well.

Thanks very much, Mark. Good luck :-)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-12-09 22:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  7:38 linux-next: Tree for Dec 8 Stephen Rothwell
2021-12-09 12:33 ` Mark Brown
     [not found]   ` <CGME20211209150028eucas1p219b6230e580770a6e93d828b467d3da3@eucas1p2.samsung.com>
2021-12-09 15:00     ` Marek Szyprowski
2021-12-09 22:07   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-08  3:30 Stephen Rothwell
2022-12-08  4:25 Stephen Rothwell
2020-12-08 10:38 Stephen Rothwell
2019-12-08  3:06 Stephen Rothwell
2017-12-08  5:02 Stephen Rothwell
2016-12-08  4:43 Stephen Rothwell
2015-12-08  4:49 Stephen Rothwell
2014-12-08 12:58 Stephen Rothwell
2011-12-08  5:12 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=20211210090716.6a991c08@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.