From: Maulik Shah <mkshah@codeaurora.org>
To: swboyd@chromium.org, agross@kernel.org, david.brown@linaro.org,
sudeep.holla@arm.com, Lorenzo.Pieralisi@arm.com
Cc: Maulik Shah <mkshah@codeaurora.org>,
lsrao@codeaurora.org, dianders@chromium.org,
rnayak@codeaurora.org, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, evgreen@chromium.org,
bjorn.andersson@linaro.org, ilina@codeaurora.org,
ulf.hansson@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/6] drivers: qcom: rpmh: fix macro to accept NULL argument
Date: Wed, 5 Feb 2020 17:56:07 +0530 [thread overview]
Message-ID: <1580905572-22712-2-git-send-email-mkshah@codeaurora.org> (raw)
In-Reply-To: <1580905572-22712-1-git-send-email-mkshah@codeaurora.org>
Device argument matches with dev variable declared in RPMH message.
Compiler reports error when the argument is NULL since the argument
matches the name of the property. Rename dev argument to device to
fix this.
Signed-off-by: Maulik Shah <mkshah@codeaurora.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
---
drivers/soc/qcom/rpmh.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/soc/qcom/rpmh.c b/drivers/soc/qcom/rpmh.c
index 035091f..3a4579d 100644
--- a/drivers/soc/qcom/rpmh.c
+++ b/drivers/soc/qcom/rpmh.c
@@ -23,7 +23,7 @@
#define RPMH_TIMEOUT_MS msecs_to_jiffies(10000)
-#define DEFINE_RPMH_MSG_ONSTACK(dev, s, q, name) \
+#define DEFINE_RPMH_MSG_ONSTACK(device, s, q, name) \
struct rpmh_request name = { \
.msg = { \
.state = s, \
@@ -33,7 +33,7 @@
}, \
.cmd = { { 0 } }, \
.completion = q, \
- .dev = dev, \
+ .dev = device, \
.needs_free = false, \
}
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-05 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 12:26 [PATCH v4 0/6] Add RSC power domain support Maulik Shah
2020-02-05 12:26 ` Maulik Shah [this message]
2020-02-05 12:26 ` [PATCH v4 2/6] drivers: qcom: rpmh: remove rpmh_flush export Maulik Shah
2020-02-05 12:26 ` [PATCH v4 3/6] dt-bindings: soc: qcom: Add RSC power domain specifier Maulik Shah
2020-02-06 21:44 ` Rob Herring
2020-02-05 12:26 ` [PATCH v4 4/6] drivers: qcom: rpmh-rsc: Add RSC power domain support Maulik Shah
2020-02-05 12:26 ` [PATCH v4 5/6] drivers: firmware: psci: Allow hierarchical topology in PC mode Maulik Shah
2020-02-05 12:26 ` [PATCH v4 6/6] arm64: dts: qcom: sc7180: Add cpuidle low power states Maulik Shah
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=1580905572-22712-2-git-send-email-mkshah@codeaurora.org \
--to=mkshah@codeaurora.org \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lsrao@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=swboyd@chromium.org \
--cc=ulf.hansson@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;
as well as URLs for NNTP newsgroup(s).