From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
kernelci-results@groups.io, bot@kernelci.org,
stable@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: kernelci/kernelci.org bisection: baseline-nfs.bootrr.deferred-probe-empty on at91sam9g20ek
Date: Thu, 18 Jan 2024 11:16:29 +0100 [thread overview]
Message-ID: <2024011816-overstate-move-4df8@gregkh> (raw)
In-Reply-To: <82cda3d4-2e46-4690-8317-855ca80fd013@sirena.org.uk>
On Wed, Jan 17, 2024 at 01:52:59PM +0000, Mark Brown wrote:
> On Wed, Jan 17, 2024 at 06:55:09AM +0100, Greg Kroah-Hartman wrote:
>
> > This is also in the following kernel releases:
> > 4.19.240 5.4.191 5.10.113
> > do they also have issues? Does 6.1 and newer work properly?
>
> Current kernels work well, I've not had reports generated for the older
> kernels but it's possible they may be forthcoming (the bisection does
> tend to send issues slowly sometimes).
>
> > And wow, this is old, nice to see it reported, but for a commit that
> > landed in April, 2022? Does that mean that no one uses this hardware?
>
> I suspect it's just me, it's in my test lab. I don't routinely test
> stable (just let KernelCI use it to test stable).
>
> > I'll be glad to revert, but should I also revert for 4.19.y and 5.4.y
> > and 5.10.y?
>
> I'd be tempted to, though it's possible it's some other related issue so
> it might be safest to hold off until there's an explicit report. Up to
> you.
I'll just drop it from 5.15.y for now, thanks!
greg k-h
next prev parent reply other threads:[~2024-01-18 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65a6ca18.170a0220.9f7f3.fa9a@mx.google.com>
2024-01-16 19:02 ` kernelci/kernelci.org bisection: baseline-nfs.bootrr.deferred-probe-empty on at91sam9g20ek Mark Brown
2024-01-17 5:55 ` Greg Kroah-Hartman
2024-01-17 13:52 ` Mark Brown
2024-01-18 10:16 ` Greg Kroah-Hartman [this message]
2024-01-18 14:33 ` Mark Brown
2024-01-22 17:45 ` Greg Kroah-Hartman
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=2024011816-overstate-move-4df8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=kernelci-results@groups.io \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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.