linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.13
Date: Mon, 28 Jun 2021 05:59:44 -0700	[thread overview]
Message-ID: <20210628125944.GA4085561@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wj7E9iTGHbqfgtaTAM09WrVzwXjda2_D59MT8D_1=54Rg@mail.gmail.com>

On Sun, Jun 27, 2021 at 03:45:50PM -0700, Linus Torvalds wrote:
> So we had quite the calm week since rc7, and I see no reason to delay
> 5.13. The shortlog for the week is tiny, with just 88 non-merge
> commits (and a few of those are just reverts).  It's a fairly random
> mix of fixes, and being so small I'd just suggest people scan the
> appended shortlog for what happened.
> 
> Of course, if the last week was small and calm, 5.13 overall is
> actually fairly large. In fact, it's one of the bigger 5.x releases,
> with over 16k commits (over 17k if you count merges), from over 2k
> developers. But it's a "big all over" kind of thing, not something
> particular that stands out as particularly unusual. Some of the extra
> size might just be because 5.12 had that extra rc week.
> 
> And with 5.13 out the door, that obviously means that the merge window
> for 5.14 will be starting tomorrow. I already have a few pull requests
> for it pending, but as usual, I'd ask people to give the final 5.13 at
> least a quick test before moving on to the exciting new pending
> stuff..
> 
Build results:
	total: 151 pass: 151 fail: 0
Qemu test results:
	total: 462 pass: 462 fail: 0

Guenter

      reply	other threads:[~2021-06-28 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 22:45 Linus Torvalds
2021-06-28 12:59 ` Guenter Roeck [this message]

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=20210628125944.GA4085561@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Linux 5.13' \
    /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

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