From: Vinod Koul <vkoul@kernel.org>
To: Frank.li@nxp.com, kishon@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: linux-phy@lists.infradead.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] phy: freescale: Initialize priv->lock
Date: Thu, 20 Nov 2025 22:41:44 +0530 [thread overview]
Message-ID: <176365870435.207696.4457416829154592287.b4-ty@kernel.org> (raw)
In-Reply-To: <20250925013806.569658-1-xiaolei.wang@windriver.com>
On Thu, 25 Sep 2025 09:38:06 +0800, Xiaolei Wang wrote:
> Initialize priv->lock to fix the following warning.
>
> WARNING: CPU: 0 PID: 12 at kernel/locking/mutex.c:577 __mutex_lock+0x70c/0x8b8
> Modules linked in:
> Hardware name: Freescale i.MX8QM MEK (DT)
> Call trace:
> __mutex_lock+0x70c/0x8b8 (P)
> mutex_lock_nested+0x24/0x30
> imx_hsio_power_on+0x4c/0x764
> phy_power_on+0x7c/0x12c
> imx_pcie_host_init+0x1d0/0x4d4
> dw_pcie_host_init+0x188/0x4b0
> imx_pcie_probe+0x324/0x6f4
> platform_probe+0x5c/0x98
> really_probe+0xbc/0x29c
> __driver_probe_device+0x78/0x12c
> driver_probe_device+0xd8/0x160
> __device_attach_driver+0xb8/0x138
> bus_for_each_drv+0x84/0xe4
> __device_attach_async_helper+0xb8/0xdc
> async_run_entry_fn+0x34/0xe0
> process_one_work+0x220/0x694
> worker_thread+0x1c0/0x36c
> kthread+0x14c/0x224
>
> [...]
Applied, thanks!
[1/1] phy: freescale: Initialize priv->lock
commit: 95e5905698983df94069e185f9eb3c67c7cf75d5
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-11-20 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 1:38 [PATCH v2] phy: freescale: Initialize priv->lock Xiaolei Wang
2025-09-25 3:58 ` Frank Li
2025-11-19 8:40 ` Neil Armstrong
2025-11-20 17:11 ` Vinod Koul [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=176365870435.207696.4457416829154592287.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.li@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xiaolei.wang@windriver.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