From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
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 May 17
Date: Thu, 24 May 2018 00:07:13 +0100 [thread overview]
Message-ID: <20180523230713.GQ4828@sirena.org.uk> (raw)
In-Reply-To: <20180522141843.GC24776@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Tue, May 22, 2018 at 03:18:43PM +0100, Mark Brown wrote:
> On Thu, May 17, 2018 at 05:06:56PM +1000, Stephen Rothwell wrote:
>
> > News: I will not be doing any linux-next releases between Friday 18 May
> > and Friday 25 May inclusive.
>
> Just noticed this, I'm going to try to cover starting tomorrow. The
> usual caveats about reduced service and reliability apply.
This isn't going to happen for today, I ran into some scripting/infrastructure
issues which effectively delayed the start of the build by about six
hours. Those are fixed now so fingers crossed things should be fine
tomorrow, I'll let the build run for a while longer today and report any
further issues but there won't be a tree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-23 23:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 7:06 linux-next: Tree for May 17 Stephen Rothwell
2018-05-17 16:55 ` linux-next: Tree for May 17 (usb/gadget/udc/aspeed-vhub/) Randy Dunlap
2018-05-17 18:03 ` linux-next: Tree for May 17 Naresh Kamboju
2018-05-17 18:34 ` linux-next: Tree for May 17 (drivers/pwm/pwm-stm32.c) Randy Dunlap
2018-05-22 14:18 ` linux-next: Tree for May 17 Mark Brown
2018-05-23 23:07 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 3:39 Stephen Rothwell
2023-05-17 2:05 Stephen Rothwell
2022-05-17 9:41 Stephen Rothwell
2019-05-17 4:21 Stephen Rothwell
2019-05-17 7:33 ` Anders Roxell
2019-05-17 9:41 ` Kirill Tkhai
2019-05-17 9:43 ` Kirill Tkhai
2019-05-17 9:53 ` Stephen Rothwell
2019-05-17 21:56 ` Palmer Dabbelt
2017-05-17 4:17 Stephen Rothwell
2016-05-17 5:04 Stephen Rothwell
2016-05-23 8:13 ` Xiong Zhou
2016-05-23 8:37 ` Stephen Rothwell
2016-05-24 4:52 ` Xiong Zhou
2013-05-17 4:21 Stephen Rothwell
2012-05-17 7:46 Stephen Rothwell
2011-05-17 4:27 Stephen Rothwell
2010-05-17 6:35 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=20180523230713.GQ4828@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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