linux-next.vger.kernel.org archive mirror
 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 Jul 28
Date: Sun, 7 Aug 2022 22:02:40 +1000	[thread overview]
Message-ID: <20220807220240.7ccec5de@canb.auug.org.au> (raw)
In-Reply-To: <YugAzWWl++ArhhPS@sirena.org.uk>

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

Hi Mark,

On Mon, 1 Aug 2022 17:35:25 +0100 Mark Brown <broonie@kernel.org> wrote:
>
> On Thu, Jul 28, 2022 at 09:02:36PM +1000, Stephen Rothwell wrote:
> 
> > News: the next linux-next release will be on Monday Aug 8th.  
> 
> I didn't notice this last week, I'll try to provide coverage for the
> remainder of this week, hopefully the merge window should help this go
> smoothly but no guarantees.

Thanks for throwing yourself on the grenade again :-)  I hope it wasn't
too onerous.  I was supposed to be absent in the second half of the
merge window.

I will be back on board tomorrow.
-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2022-08-07 12:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 11:02 linux-next: Tree for Jul 28 Stephen Rothwell
2022-08-01 16:35 ` Mark Brown
2022-08-07 12:02   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-28  4:50 Stephen Rothwell
2021-07-28 23:46 Mark Brown
2020-07-28 11:57 Stephen Rothwell
2017-07-28  5:45 Stephen Rothwell
2016-07-28  5:05 Stephen Rothwell
2015-07-28  6:37 Stephen Rothwell
2014-07-28 11:27 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=20220807220240.7ccec5de@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).