From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, florian.fainelli@broadcom.com,
pavel@denx.de
Subject: Re: [PATCH 6.7 000/707] 6.7.11-rc2 review
Date: Tue, 26 Mar 2024 18:28:57 +0100 [thread overview]
Message-ID: <2024032644-speech-reformist-e41e@gregkh> (raw)
In-Reply-To: <cb00ee0c-ed03-4351-9782-99eab1894234@sirena.org.uk>
On Tue, Mar 26, 2024 at 04:16:13PM +0000, Mark Brown wrote:
> On Mon, Mar 25, 2024 at 08:00:03AM -0400, Sasha Levin wrote:
> >
> > This is the start of the stable review cycle for the 6.7.11 release.
> > There are 707 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed Mar 27 12:00:02 PM UTC 2024.
> > Anything received after that time might be too late.
>
> This is broken on at least the original Raspberry Pi, no output appears
> on the console. Bisection tells me that the problem is introduced by
> d7303ef54fae6 ("printk: Disable passing console lock owner completely
> during panic()") though I'm not entirely sure I believe this. I've got
> some bisects running on other 32 bit arm platforms with the same
> symptoms which I suspect will turn out to be the same issue, and v6.8 is
> failing in what looks like the same way.
>
> BTW I did ask to be CCed on the review mails, it'd make life a bit
> easier.
Sorry, that was on my side, I'll add you soon to the scripts.
greg k-h
next prev parent reply other threads:[~2024-03-26 17:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:00 [PATCH 6.7 000/707] 6.7.11-rc2 review Sasha Levin
2024-03-25 17:43 ` Daniel Díaz
2024-03-25 18:14 ` Sami Tolvanen
2024-03-25 19:47 ` Daniel Díaz
2024-03-26 11:23 ` Sasha Levin
2024-03-25 17:57 ` SeongJae Park
2024-03-25 18:22 ` Naresh Kamboju
2024-03-25 19:07 ` Pavel Machek
2024-03-25 20:05 ` Justin Forbes
2024-03-25 20:39 ` Florian Fainelli
2024-03-26 2:09 ` Bagas Sanjaya
2024-03-26 9:04 ` Ron Economos
2024-03-26 16:16 ` Mark Brown
2024-03-26 17:28 ` Greg KH [this message]
2024-03-26 17:35 ` Mark Brown
2024-03-26 17:00 ` Shuah Khan
2024-03-26 19:52 ` Conor Dooley
2024-03-26 20:48 ` Shreeya Patel
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=2024032644-speech-reformist-e41e@gregkh \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@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