All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: sound/soc/soc-dapm.c:1023:4: error: implicit declaration of function 'regulator_allow_bypass'
Date: Sat, 8 Sep 2012 09:51:06 +0800	[thread overview]
Message-ID: <20120908015106.GA19743@localhost> (raw)
In-Reply-To: <20120908014450.GB19345@localhost>

[add the missing subject line..]

On Sat, Sep 08, 2012 at 09:44:50AM +0800, Fengguang Wu wrote:
> Hi Mark,
> 
> FYI, kernel build failed on
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> head:   e8bb382aa74747f23e2903c15e48e9f06de5c60a
> commit: 9ad4ba77112a3700129cdb142796a54680baa266 [100/103] ASoC: dapm: Allow regulators to bypass as well as disable when idle
> config: x86_64-allmodconfig (attached as .config)
> 
> All related error/warning messages:
> 
> sound/soc/soc-dapm.c: In function 'dapm_regulator_event':
> sound/soc/soc-dapm.c:1023:4: error: implicit declaration of function 'regulator_allow_bypass' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> 
> vim +1023 sound/soc/soc-dapm.c
>   1018	{
>   1019		int ret;
>   1020	
>   1021		if (SND_SOC_DAPM_EVENT_ON(event)) {
>   1022			if (w->invert & SND_SOC_DAPM_REGULATOR_BYPASS) {
> > 1023				ret = regulator_allow_bypass(w->regulator, true);
>   1024				if (ret != 0)
>   1025					dev_warn(w->dapm->dev,
>   1026						 "Failed to bypass %s: %d\n",
>   1027						 w->name, ret);
>   1028			}
> 
> ---
> 0-DAY kernel build testing backend         Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: sound/soc/soc-dapm.c:1023:4: error: implicit declaration of function 'regulator_allow_bypass'
Date: Sat, 08 Sep 2012 01:51:06 +0000	[thread overview]
Message-ID: <20120908015106.GA19743@localhost> (raw)
In-Reply-To: <20120908014450.GB19345@localhost>

[add the missing subject line..]

On Sat, Sep 08, 2012 at 09:44:50AM +0800, Fengguang Wu wrote:
> Hi Mark,
> 
> FYI, kernel build failed on
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> head:   e8bb382aa74747f23e2903c15e48e9f06de5c60a
> commit: 9ad4ba77112a3700129cdb142796a54680baa266 [100/103] ASoC: dapm: Allow regulators to bypass as well as disable when idle
> config: x86_64-allmodconfig (attached as .config)
> 
> All related error/warning messages:
> 
> sound/soc/soc-dapm.c: In function 'dapm_regulator_event':
> sound/soc/soc-dapm.c:1023:4: error: implicit declaration of function 'regulator_allow_bypass' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> 
> vim +1023 sound/soc/soc-dapm.c
>   1018	{
>   1019		int ret;
>   1020	
>   1021		if (SND_SOC_DAPM_EVENT_ON(event)) {
>   1022			if (w->invert & SND_SOC_DAPM_REGULATOR_BYPASS) {
> > 1023				ret = regulator_allow_bypass(w->regulator, true);
>   1024				if (ret != 0)
>   1025					dev_warn(w->dapm->dev,
>   1026						 "Failed to bypass %s: %d\n",
>   1027						 w->name, ret);
>   1028			}
> 
> ---
> 0-DAY kernel build testing backend         Open Source Technology Centre
> Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation


       reply	other threads:[~2012-09-08  1:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120908014450.GB19345@localhost>
2012-09-08  1:51 ` Fengguang Wu [this message]
2012-09-08  1:51   ` sound/soc/soc-dapm.c:1023:4: error: implicit declaration of function 'regulator_allow_bypass' Fengguang Wu

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=20120908015106.GA19743@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kernel-janitors@vger.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.