archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: Linus Torvalds <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Linux 5.17
Date: Mon, 21 Mar 2022 07:58:22 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Mar 20, 2022 at 01:34:21PM -0700, Linus Torvalds wrote:
> So we had an extra week of at the end of this release cycle, and I'm
> happy to report that it was very calm indeed.  We could probably have
> skipped it with not a lot of downside, but we did get a few
> last-minute reverts and fixes in and avoid some brown-paper bugs that
> would otherwise have been stable fodder, so it's all good.
> And that calm last week can very much be seen from the appended
> shortlog - there really aren't a lot of commits in here, and it's all
> pretty small. Most of it is in drivers (net, usb, drm), with some core
> networking, and some tooling updates too.
> It really is small enough that you can just scroll through the details
> below, and the one-liner summaries will give a good flavor of what
> happened last week.
> Of course, this means that the merge window for 5.18 will be open
> starting tomorrow, and I already have about a dozen pull requests
> waiting in my inbox. I appreciate the early pull requests: it gives me
> that warm and fuzzy feeling of "this was all ready in plenty of time".
> Judging by the statistics in linux-next, it looks like 5.18 will be a
> bit bigger than 5.17 was, but hopefully without some of the drama.
> So go test this, and we'll get 5.18 started tomorrow.

Build results:
	total: 155 pass: 155 fail: 0
Qemu test results:
	total: 488 pass: 488 fail: 0


  parent reply	other threads:[~2022-03-21 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 20:34 Linux 5.17 Linus Torvalds
2022-03-21 10:16 ` Build regressions/improvements in v5.17 Geert Uytterhoeven
2022-03-21 14:48   ` Geert Uytterhoeven
2022-03-21 14:58 ` Guenter Roeck [this message]
2022-03-21 16:54   ` Linux 5.17 Linus Torvalds

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).