public inbox for linux-next@vger.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 18
Date: Thu, 19 Dec 2024 08:14:04 +1100	[thread overview]
Message-ID: <20241219081404.28cc069a@canb.auug.org.au> (raw)
In-Reply-To: <6242bac5-bf75-4cf2-8baf-62df8d159792@sirena.org.uk>

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

Hi Mark,

On Wed, 18 Dec 2024 14:28:11 +0000 Mark Brown <broonie@kernel•org> wrote:
>
> On Wed, Dec 18, 2024 at 03:32:28PM +1100, Stephen Rothwell wrote:
> 
> > News: there will be no linux-next releases after this week until
> > January 6.  
> 
> I'm taking similar holidays, it's possible I might do some runs but I'd
> not count on it.

No worries, hopefully it will be pretty quiet anyway.  There is plenty
of time for me to catch up in January.  Have a good break.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2024-12-18 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18  4:32 linux-next: Tree for Dec 18 Stephen Rothwell
2024-12-18 14:28 ` Mark Brown
2024-12-18 21:14   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-18 11:12 Stephen Rothwell
2025-12-18 11:27 ` Mark Brown
2023-12-18  7:49 Stephen Rothwell
2020-12-18  5:33 Stephen Rothwell
2019-12-18  4:29 Stephen Rothwell
2018-12-18  7:42 Stephen Rothwell
2017-12-18  6:26 Stephen Rothwell
2015-12-18  7:51 Stephen Rothwell
2014-12-18  4:54 Stephen Rothwell
2013-12-18  7:40 Stephen Rothwell
2012-12-18  2:51 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=20241219081404.28cc069a@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