From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Krzysztof Kozlowski <krzk@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 Apr 24
Date: Fri, 26 Apr 2024 06:58:07 +1000 [thread overview]
Message-ID: <20240426065807.130c7140@canb.auug.org.au> (raw)
In-Reply-To: <f43600b5-dbb0-43a0-bd82-f950f9604b28@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Hi Krzysztof,
On Thu, 25 Apr 2024 08:15:14 +0200 Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 24/04/2024 12:21, Stephen Rothwell wrote:
> >
> > News: there will be no linux-next release tomorrow.
> >
> > Changes since 20240423:
>
> If you did not publish next for 25 Apr, maybe you can refetch
> memory-controllers tree (krzk/linux-mem-ctrl.git)?
>
> I applied set of patches yesterday evening and I got build results after
> I finished working, so did not react on multiple failures caused by
> these patches.
>
> I noticed the failures now, I dropped patchset and refreshed my for-next
> branch.
I did not do a linux-next release yesterday, so it should all be good
today, I guess.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-04-25 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 10:21 linux-next: Tree for Apr 24 Stephen Rothwell
2024-04-25 6:15 ` Krzysztof Kozlowski
2024-04-25 20:58 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 16:00 broonie
2020-04-24 7:48 Stephen Rothwell
2019-04-24 9:12 Stephen Rothwell
2018-04-24 4:53 Stephen Rothwell
2017-05-05 18:55 Andrew Jones
2017-04-24 8:10 Stephen Rothwell
2017-04-24 15:44 ` Paul Gortmaker
2015-04-24 4:50 Stephen Rothwell
2014-04-24 6:26 Stephen Rothwell
2013-04-24 8:07 Stephen Rothwell
2012-04-24 5:43 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=20240426065807.130c7140@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=krzk@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).