From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-kernel@vger.kernel.org, rjendra@qti.qualcomm.com
Subject: [PATCH v1 2/3] regmap: add dummy regmap_can_raw_write() to header
Date: Wed, 13 Apr 2016 18:39:13 +0100 [thread overview]
Message-ID: <1460569154-25030-3-git-send-email-srinivas.kandagatla@linaro.org> (raw)
In-Reply-To: <1460569154-25030-1-git-send-email-srinivas.kandagatla@linaro.org>
This patch adds dummy function for regmap_can_raw_write() in the header
file, so that the code can be atleast compiled without regmap enabled.
This kind of setup is mostly tested using randomconfig or zero
day-testing.
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
---
include/linux/regmap.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/linux/regmap.h b/include/linux/regmap.h
index be3da4c..c060b9b 100644
--- a/include/linux/regmap.h
+++ b/include/linux/regmap.h
@@ -1052,6 +1052,12 @@ static inline bool regmap_can_raw_read(struct regmap *map)
return false;
}
+static inline bool regmap_can_raw_write(struct regmap *map)
+{
+ WARN_ONCE(1, "regmap API is disabled");
+ return false;
+}
+
static inline int regmap_register_patch(struct regmap *map,
const struct reg_sequence *regs,
int num_regs)
--
2.5.0
next prev parent reply other threads:[~2016-04-13 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 17:39 [PATCH v1 0/3] nvmem: core: fix regmap accessor usage Srinivas Kandagatla
2016-04-13 17:39 ` [PATCH v1 1/3] regmap: add regmap_can_raw_read() api Srinivas Kandagatla
2016-04-14 5:58 ` Mark Brown
2016-04-13 17:39 ` Srinivas Kandagatla [this message]
2016-04-14 6:45 ` [PATCH v1 2/3] regmap: add dummy regmap_can_raw_write() to header Mark Brown
2016-04-13 17:39 ` [PATCH v1 3/3] nvmem: core: fix regmap accessor usage Srinivas Kandagatla
2016-04-14 6:42 ` Mark Brown
2016-04-14 12:35 ` Srinivas Kandagatla
2016-04-14 15:18 ` Mark Brown
2016-04-14 16:48 ` Srinivas Kandagatla
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=1460569154-25030-3-git-send-email-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=rjendra@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).