All of lore.kernel.org
 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.2-rc5
Date: Sun, 22 Jan 2023 13:51:05 -0800	[thread overview]
Message-ID: <20230122215105.GA1788657@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wg+E9tTCrSqBOxejUX11f8ebyRWQ+4exC=cmOEupX_d7Q@mail.gmail.com>

On Sat, Jan 21, 2023 at 04:44:06PM -0800, Linus Torvalds wrote:
> Ok, so I thought we were back to normal after the winter holidays at
> rc4. Now, a week later, I think I was mistaken - we have fairly
> sizable rc5, so I suspect there was still pent up testing and fixes
> from people being off.
> 
> Anyway, I am expecting to do an rc8 this release regardless, just
> because we effectively had a lost week or two in the early rc's, so a
> sizable rc5 doesn't really worry me. I do hope we're done with the
> release candidates growing, though.
> 
> Anyway, there's a bit of everything in rc5: various driver updates
> (gpu, rdma, networking, tty, usb..), some architecture updates (mostly
> loongarch and arm64), some filesystem updates, some core networking,
> and tooling.
> 
> The shortlog is appended as usual. Nothing particularly odd stands out to me.
> 
> Please do test,
> 

Nothing to report from my side.

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

Guenter

      parent reply	other threads:[~2023-01-22 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  0:44 Linux 6.2-rc5 Linus Torvalds
2023-01-22 11:51 ` Build regressions/improvements in v6.2-rc5 Geert Uytterhoeven
2023-01-22 13:49 ` Linux 6.2-rc5 Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-22 19:17   ` Linus Torvalds
2023-01-22 21:51 ` 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=20230122215105.GA1788657@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.