public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Csókás Bence" <Csokas.Bence@prolan.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Sasha Levin <sashal@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Marc Kleine-Budde" <mkl@pengutronix.de>,
	Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: Linux 6.0-rc4
Date: Mon, 12 Sep 2022 07:00:20 +0000	[thread overview]
Message-ID: <7488bc1ff5b34b7aa79ef31c7d19f5f2@prolan.hu> (raw)
In-Reply-To: <CAHk-=wj1obPoTu1AHj9Bd_BGYjdjDyPP+vT5WMj8eheb3A9WHw@mail.gmail.com>

Hey there, perpetrator here.

It seems b353b241f1eb9 is botched, and may be reverted. I am working
on a replacement fix, but I am working remotely. Please do not revert
f79959220fa5 just yet.

Bence

> Let's bring in the guilty party and related people..
> 
> It looks like b353b241f1eb9 ("net: fec: Use a spinlock to guard
> `fep->ptp_clk_on`") is not sufficient to fix the problems caused by
> f79959220fa5 ("fec: Restart PPS after link state change"), and in fact
> just causes more issues.
> 
> By now I suspect that both of those just have to be reverted.
> 
> Hmm?
> 
>               Linus

      reply	other threads:[~2022-09-12  7:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 20:22 Linux 6.0-rc4 Linus Torvalds
2022-09-05  7:19 ` Build regressions/improvements in v6.0-rc4 Geert Uytterhoeven
2022-09-05  7:46   ` Geert Uytterhoeven
2022-09-06 21:42     ` Kees Cook
2022-09-07 23:47     ` Kees Cook
2022-09-05 12:56 ` Linux 6.0-rc4 Guenter Roeck
2022-09-10 17:44   ` Linus Torvalds
2022-09-10 18:13     ` Guenter Roeck
2022-09-10 21:32       ` Linus Torvalds
2022-09-12  7:00         ` Csókás Bence [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=7488bc1ff5b34b7aa79ef31c7d19f5f2@prolan.hu \
    --to=csokas.bence@prolan.hu \
    --cc=davem@davemloft.net \
    --cc=francesco.dolcini@toradex.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mkl@pengutronix.de \
    --cc=sashal@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