From: Vinod Koul <vkoul@kernel.org>
To: Kishon Vijay Abraham I <kishon@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend
Date: Thu, 17 Oct 2024 21:01:19 +0530 [thread overview]
Message-ID: <172917907975.278159.209159976898815690.b4-ty@kernel.org> (raw)
In-Reply-To: <20240911115253.10920-1-johan+linaro@kernel.org>
On Wed, 11 Sep 2024 13:52:49 +0200, Johan Hovold wrote:
> When working on suspend support for Qualcomm platforms like x1e80100, I
> ran into a NULL-pointer dereference in one of the QMP drivers. Turns out
> this issue has since been reproduced in two more drivers.
>
> Johan
>
>
> [...]
Applied, thanks!
[1/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend
commit: bd9e4d4a3b127686efc60096271b0a44c3100061
[2/4] phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
commit: 29240130ab77c80bea1464317ae2a5fd29c16a0c
[3/4] phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend
commit: 34c21f94fa1e147a19b54b6adf0c93a623b70dd8
[4/4] phy: qcom: qmp-usb: move driver data initialisation earlier
commit: 1dd196f9004848d0318e8831f962cc76255431d8
Best regards,
--
~Vinod
prev parent reply other threads:[~2024-10-17 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 11:52 [PATCH 0/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend Johan Hovold
2024-09-11 11:52 ` [PATCH 1/4] " Johan Hovold
2024-09-11 11:52 ` [PATCH 2/4] phy: qcom: qmp-usb-legacy: " Johan Hovold
2024-09-11 11:52 ` [PATCH 3/4] phy: qcom: qmp-usbc: " Johan Hovold
2024-09-11 11:52 ` [PATCH 4/4] phy: qcom: qmp-usb: move driver data initialisation earlier Johan Hovold
2024-09-11 11:57 ` Johan Hovold
2024-09-11 19:01 ` [PATCH 0/4] phy: qcom: qmp-usb: fix NULL-deref on runtime suspend Dmitry Baryshkov
2024-10-16 7:43 ` Johan Hovold
2024-10-17 15:31 ` 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=172917907975.278159.209159976898815690.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=kishon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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