public inbox for linux-kernel@vger.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>,
	"Csókás Bence" <csokas.bence@prolan.hu>,
	"Jakub Kicinski" <kuba@kernel.org>
Subject: Re: Linux 6.0-rc6
Date: Sun, 18 Sep 2022 21:06:53 -0700	[thread overview]
Message-ID: <20220919040653.GA1840059@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wi=gtuSO8Yz8LDubkMk7TiMsZxpypt9S10jeZRkyaBFnA@mail.gmail.com>

On Sun, Sep 18, 2022 at 01:56:17PM -0700, Linus Torvalds wrote:
> So this is an artificially small -rc release, because this past week
> we had the Maintainers' Summit in Dublin (along with OSS EU and LPC
> 2022), so we've had a lot of maintainers traveling.
> 
> Or - putting my ridiculously optimistic hat on - maybe things are just
> so nice and stable that there just weren't all that many fixes?
> 
> Yeah, I know which scenario I'm betting on, but hope springs eternal.
> 
> Regardless, things look fine. I am expecting rc7 to be larger than
> usual due to pull requests having shifted one week later, and in the
> worst case that might mean that I might feel like we need an extra
> rc8, but for now I'm going to assume it's not going to be _that_
> noticeable and hope we'll just keep to the regular schedule.
> 
> But it would be lovely if everybody gave this some extra tender loving
> care in the form of extra testing...
> 

Build results:
	total: 149 pass: 149 fail: 0
Qemu test results:
	total: 490 pass: 489 fail: 1
Failed tests:
	mcf5208evb:m5208:m5208evb_defconfig:initrd

TL;DR: Patches / reverts needed to fix known regressions

Revert "net: fec: Use a spinlock to guard `fep->ptp_clk_on`"
Revert "fec: Restart PPS after link state change"
    revert b353b241f1eb
    revert f79959220fa5
    Rationale:
	The patches result in various tracebacks and crashes.
	https://lore.kernel.org/netdev/20220827160922.642zlcd5foopozru@pengutronix.de/

The need to revert those patches has been discussed repeatedly,
so going into details seems pointless.

Guenter

  reply	other threads:[~2022-09-19  4:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 20:56 Linux 6.0-rc6 Linus Torvalds
2022-09-19  4:06 ` Guenter Roeck [this message]
2022-09-19 14:28   ` Jakub Kicinski
2022-09-19 15:02     ` Guenter Roeck
2022-09-19  6:50 ` Build regressions/improvements in v6.0-rc6 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=20220919040653.GA1840059@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=csokas.bence@prolan.hu \
    --cc=kuba@kernel.org \
    --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