From: Lars-Peter Clausen <lars@metafoo.de>
To: Olof Johansson <olof@lixom.net>, broonie@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: provide dummy regmap_exit()
Date: Tue, 25 Nov 2014 21:39:58 +0100 [thread overview]
Message-ID: <5474E91E.6000401@metafoo.de> (raw)
In-Reply-To: <1416946910-23329-1-git-send-email-olof@lixom.net>
On 11/25/2014 09:21 PM, Olof Johansson wrote:
> Fixes build error:
>
> sound/soc/soc-core.c: In function 'snd_soc_component_exit_regmap':
> sound/soc/soc-core.c:2644:2: error: implicit declaration of function 'regmap_exit' [-Werror=implicit-function-declaration]
> regmap_exit(component->regmap);
>
> Due to the other regmap functions providing appropriate stubs when
> !CONFIG_REGMAP, but this one is missing. Add it.
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
I did a different patch for this I was just about to send. This looks good
as well I guess, but ...
> ---
> include/linux/regmap.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/include/linux/regmap.h b/include/linux/regmap.h
> index 4419b99..efb58a0 100644
> --- a/include/linux/regmap.h
> +++ b/include/linux/regmap.h
> @@ -737,6 +737,11 @@ static inline struct regmap *dev_get_regmap(struct device *dev,
> return NULL;
> }
>
> +static inline void regmap_exit(struct regmap *map)
> +{
> + return;
... but we really don't need the return here.
> +}
> +
> static inline struct device *regmap_get_device(struct regmap *map)
> {
> WARN_ONCE(1, "regmap API is disabled");
>
next prev parent reply other threads:[~2014-11-25 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 20:21 [PATCH] regmap: provide dummy regmap_exit() Olof Johansson
2014-11-25 20:39 ` Lars-Peter Clausen [this message]
2014-11-25 21:03 ` [PATCH v2] " Olof Johansson
2014-11-25 21:14 ` Mark Brown
2014-11-25 21:18 ` Mark Brown
2014-11-25 21:27 ` Olof Johansson
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=5474E91E.6000401@metafoo.de \
--to=lars@metafoo.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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.