mirror of https://lore.kernel.org/lkml/
 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 6.1-rc5
Date: Mon, 14 Nov 2022 15:08:28 -0800	[thread overview]
Message-ID: <20221114230828.GA2089561@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wicGu7PD25w7BCdvxRcs6Yvo-BPwCkzSYjM2CYtDjz2kg@mail.gmail.com>

On Sun, Nov 13, 2022 at 01:29:20PM -0800, Linus Torvalds wrote:
> Another week, another rc.
> 
> Did things calm down and shrink this week? No. We've got about as many
> commits in rc5 as we had in rc4. It's not outrageously big, but it's
> certainly on the bigger side for this timeframe.
> 
> Am I getting worried? Not yet. There's nothing particularly worrisome
> in here, and the rc5 changes are just a little bit of everything, so
> I'm hoping it's just that it's one of those timing things and all the
> pull requests came in this week, and it's going to calm down now.
> 
> But we'll see. If things don't start calming down, this may be one of
> those releases that need an extra week. It wasn't a particularly big
> merge window, but I don't particularly like how the rc's keep being on
> the bigger side.
> 
> Anyway, lots of small fixes, fairly spread out (the diffstat looks
> fairly flat apart from some maple tree tests moving to the testing
> subdirectory). Nothing really stands out, the stats all look normal
> apart from the "just slightly more than usual". Drivers, networking,
> architecture fixes, with some smattering of noise elsewhere.
> 

Nothing to report from my side.

Build results:
	total: 152 pass: 152 fail: 0
Qemu test results:
	total: 500 pass: 500 fail: 0

Guenter

  reply	other threads:[~2022-11-14 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 21:29 Linus Torvalds
2022-11-14 23:08 ` Guenter Roeck [this message]
2022-11-16  7:45 ` Build regressions/improvements in v6.1-rc5 Geert Uytterhoeven

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=20221114230828.GA2089561@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®