From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: YueHaibing <yuehaibing@huawei.com>,
cezary.rojewski@intel.com, liam.r.girdwood@linux.intel.com,
yang.jie@linux.intel.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, gregkh@linuxfoundation.org, allison@lohutok.net,
tglx@linutronix.de, alexios.zavras@intel.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: Intel: sst: Add missing include <linux/io.h>
Date: Mon, 2 Dec 2019 11:32:18 -0600 [thread overview]
Message-ID: <62e5bb2c-14a9-66d0-c89e-c38b5550fb86@linux.intel.com> (raw)
In-Reply-To: <20191128135853.8360-1-yuehaibing@huawei.com>
On 11/28/19 7:58 AM, YueHaibing wrote:
> Fix build error:
>
> sound/soc/intel/atom/sst/sst.c: In function intel_sst_interrupt_mrfld:
> sound/soc/intel/atom/sst/sst.c:93:5: error: implicit declaration of function memcpy_fromio;
> did you mean memcpy32_fromio? [-Werror=implicit-function-declaration]
> memcpy_fromio(msg->mailbox_data,
> ^~~~~~~~~~~~~
> memcpy32_fromio
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
that looks legit, we had similar reports for SoundWire.
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> ---
> sound/soc/intel/atom/sst/sst.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sound/soc/intel/atom/sst/sst.c b/sound/soc/intel/atom/sst/sst.c
> index fbecbb7..68bcec5 100644
> --- a/sound/soc/intel/atom/sst/sst.c
> +++ b/sound/soc/intel/atom/sst/sst.c
> @@ -14,6 +14,7 @@
> #include <linux/module.h>
> #include <linux/fs.h>
> #include <linux/interrupt.h>
> +#include <linux/io.h>
> #include <linux/firmware.h>
> #include <linux/pm_runtime.h>
> #include <linux/pm_qos.h>
>
next prev parent reply other threads:[~2019-12-02 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 13:58 YueHaibing
2019-12-02 17:32 ` Pierre-Louis Bossart [this message]
2019-12-03 13:59 ` Applied "ASoC: Intel: sst: Add missing include <linux/io.h>" to the asoc tree Mark Brown
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=62e5bb2c-14a9-66d0-c89e-c38b5550fb86@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®