From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Dragan Simic" <dsimic@manjaro.org>,
"Robin Murphy" <robin.murphy@arm.com>
Cc: "Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, <linux-leds@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: BUG: Circular locking dependency on netdev led trigger on NanoPi R5S
Date: Thu, 31 Jul 2025 12:47:31 +0200 [thread overview]
Message-ID: <DBQ6ISOKV0XR.22W3OAALUKIHQ@cknow.org> (raw)
In-Reply-To: <475ee9ae8cdca5ce86b708fe0ade7c9d@manjaro.org>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Wed Jul 30, 2025 at 9:50 PM CEST, Dragan Simic wrote:
> I've spent some time digging through the LED subsystem, which I'm
> already somewhat familiar with, and I think I've narrowed down the
> root cause of this deadlock.
>
> I'll send a preliminary patch soon, after I make sure that the root
> cause is identified correctly, and I hope Diederik will be willing
> to test the patch. If so, and if the patch checks out to be the
> cure, I'll prepare and submit a proper patch, of course.
Sure, but AFAIC you can send it to the ML(s) directly as well.
Please do CC me as I'm only subscribed to the linux-rockchip ML.
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-07-31 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 17:48 Diederik de Haas
2025-07-25 18:12 ` Robin Murphy
2025-07-30 19:50 ` Dragan Simic
2025-07-31 10:47 ` Diederik de Haas [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=DBQ6ISOKV0XR.22W3OAALUKIHQ@cknow.org \
--to=didi.debian@cknow.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsimic@manjaro.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@kernel.org \
--cc=robin.murphy@arm.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®