From: Dan Carpenter <dan.carpenter@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: [PATCH 0/4] remoteproc: qcom: Fix devm_ioremap_resource_wc() checking
Date: Sat, 29 Nov 2025 17:50:47 +0300 [thread overview]
Message-ID: <cover.1764427595.git.dan.carpenter@linaro.org> (raw)
The devm_ioremap_resource_wc() function returns error pointers and not
NULL. I don't know, if you'll want to fold these patches all together
or not. Or into the original patch, perhaps?
Dan Carpenter (4):
remoteproc: qcom: Fix a NULL vs IS_ERR() check in
adsp_alloc_memory_region()
remoteproc: qcom: pas: Fix a couple NULL vs IS_ERR() bugs
remoteproc: qcom: Fix NULL vs IS_ERR() bug in
q6v5_alloc_memory_region()
remoteproc: qcom_wcnss: Fix NULL vs IS_ERR() bug in
wcnss_alloc_memory_region()
drivers/remoteproc/qcom_q6v5_adsp.c | 5 +++--
drivers/remoteproc/qcom_q6v5_pas.c | 8 ++++----
drivers/remoteproc/qcom_q6v5_wcss.c | 4 ++--
drivers/remoteproc/qcom_wcnss.c | 4 ++--
4 files changed, 11 insertions(+), 10 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-29 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 14:50 Dan Carpenter [this message]
2025-11-29 14:50 ` [PATCH 1/4] remoteproc: qcom_q6v5_adsp: Fix a NULL vs IS_ERR() check in adsp_alloc_memory_region() Dan Carpenter
2025-11-29 14:51 ` [PATCH 2/4] remoteproc: qcom: pas: Fix a couple NULL vs IS_ERR() bugs Dan Carpenter
2025-11-29 14:51 ` [PATCH 3/4] remoteproc: qcom: q6v5: Fix NULL vs IS_ERR() bug in q6v5_alloc_memory_region() Dan Carpenter
2025-11-29 14:51 ` [PATCH 4/4] remoteproc: qcom_wcnss: Fix NULL vs IS_ERR() bug in wcnss_alloc_memory_region() Dan Carpenter
2025-12-01 11:26 ` [PATCH 0/4] remoteproc: qcom: Fix devm_ioremap_resource_wc() checking Konrad Dybcio
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=cover.1764427595.git.dan.carpenter@linaro.org \
--to=dan.carpenter@linaro.org \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.