From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: Devices not instantiating on Alta
Date: Wed, 14 May 2025 10:48:39 +0200 [thread overview]
Message-ID: <aCRY5_LOGKxO4pVz@finisterre.sirena.org.uk> (raw)
In-Reply-To: <1jikm3y4zb.fsf@starbuckisacylon.baylibre.com>
[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]
On Wed, May 14, 2025 at 10:24:40AM +0200, Jerome Brunet wrote:
> On Wed 14 May 2025 at 10:13, Mark Brown <broonie@kernel.org> wrote:
> > For the past few days in -next I've been seeing the reset controller and
> > audio subsystem failing to probe on Alta, I *think* the audio is a knock
> > on effect of the reset controller. I didn't spot a smoking gun in the
> > log:
> > https://lava.sirena.org.uk/scheduler/job/1388164#L4875
> Maybe I missed it but where can I get the -next sha1 used and associated
> config used for this test ? I'd like to give it a try.
The SHA is in the job title at the top of the link (IIRC that log is for
yesterday's -next since today's isn't out yet but it's been at least
since Monday), the config is just a plain arm64 defconfig.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-05-14 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 8:13 Mark Brown
2025-05-14 8:24 ` Jerome Brunet
2025-05-14 8:48 ` Mark Brown [this message]
2025-05-15 11:36 ` Mark Brown
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=aCRY5_LOGKxO4pVz@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
/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
all inboxes | Powered by JetHome®