public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 17 Jan 2024 06:55:09 +0100	[thread overview]
Message-ID: <2024011716-undocked-external-9eae@gregkh> (raw)
In-Reply-To: <845b3053-d47b-4717-9665-79b120da133b@sirena.org.uk>

On Tue, Jan 16, 2024 at 07:02:19PM +0000, Mark Brown wrote:
> On Tue, Jan 16, 2024 at 10:25:28AM -0800, KernelCI bot wrote:
> 
> The KernelCI bisection bot has identified bc7d0133181e5f33aca ("ASoC:

Nit, typo in your sha1 here :(

> atmel: Remove system clock tree configuration for at91sam9g20ek") from
> the v5.15 stable tree as causing something to fail to probe on
> at91sam9g20ek, most likely the audio driver though I didn't pull the
> logs to verify.  The commit isn't a particularly obvious one for
> backporting.
> 
> Full bisection report below.

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?

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'll be glad to revert, but should I also revert for 4.19.y and 5.4.y
and 5.10.y?

thanks,

greg k-h

  reply	other threads:[~2024-01-17  5:55 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 [this message]
2024-01-17 13:52     ` Mark Brown
2024-01-18 10:16       ` Greg Kroah-Hartman
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=2024011716-undocked-external-9eae@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox