From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andrew Halaney <ahalaney@redhat.com>
Subject: [PATCH v2 0/2] soc: qcom: pmic_glink: fix client handling
Date: Wed, 03 Apr 2024 06:10:56 +0300 [thread overview]
Message-ID: <20240403-pmic-glink-fix-clients-v2-0-aed4e02baacc@linaro.org> (raw)
Fix two issues with the way the pmic_glink driver handles its clients.
First issue is mostly theoretical, while the second issue can easily be
reproduced if the drivers are built as modules.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
Changes in v2:
- Also take a lock at pmic_glink_rpmsg_callback() (Andrew Halaney)
- Link to v1: https://lore.kernel.org/r/20240402-pmic-glink-fix-clients-v1-0-885440b81c65@linaro.org
---
Dmitry Baryshkov (2):
soc: qcom: pmic_glink: don't traverse clients list without a lock
soc: qcom: pmic_glink: notify clients about the current state
drivers/soc/qcom/pmic_glink.c | 9 +++++++++
1 file changed, 9 insertions(+)
---
base-commit: a6bd6c9333397f5a0e2667d4d82fef8c970108f2
change-id: 20240402-pmic-glink-fix-clients-5df0bab3e871
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
next reply other threads:[~2024-04-03 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 3:10 Dmitry Baryshkov [this message]
2024-04-03 3:10 ` [PATCH v2 1/2] soc: qcom: pmic_glink: don't traverse clients list without a lock Dmitry Baryshkov
2024-04-03 15:17 ` Andrew Halaney
2024-04-05 16:56 ` Mukesh Ojha
2024-04-03 3:10 ` [PATCH v2 2/2] soc: qcom: pmic_glink: notify clients about the current state Dmitry Baryshkov
2024-04-05 16:52 ` Mukesh Ojha
2024-04-05 15:43 ` [PATCH v2 0/2] soc: qcom: pmic_glink: fix client handling Xilin Wu
2024-04-21 22:29 ` Bjorn Andersson
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=20240403-pmic-glink-fix-clients-v2-0-aed4e02baacc@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.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
all inboxes | Powered by JetHome®