From: "Agrawal, Akshu" <aagrawal2@amd.com>
To: YueHaibing <yuehaibing@huawei.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, akshu.agrawal@amd.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoc: amd: acp3x: Add missing include <linux/io.h>
Date: Thu, 5 Mar 2020 15:37:05 +0530 [thread overview]
Message-ID: <5d205b07-32c4-db9e-76bb-936bca3247ce@amd.com> (raw)
In-Reply-To: <20200304084057.44764-1-yuehaibing@huawei.com>
On 3/4/2020 2:10 PM, YueHaibing wrote:
> gcc 7.4.0 build fails:
>
> In file included from sound/soc/amd/acp3x-rt5682-max9836.c:20:0:
> sound/soc/amd/raven/acp3x.h: In function rv_readl:
> sound/soc/amd/raven/acp3x.h:113:9: error: implicit declaration of function readl; did you mean rv_readl? [-Werror=implicit-function-declaration]
> return readl(base_addr - ACP3x_PHY_BASE_ADDRESS);
> ^~~~~
> rv_readl
> sound/soc/amd/raven/acp3x.h: In function rv_writel:
> sound/soc/amd/raven/acp3x.h:118:2: error: implicit declaration of function writel; did you mean rv_writel? [-Werror=implicit-function-declaration]
> writel(val, base_addr - ACP3x_PHY_BASE_ADDRESS);
> ^~~~~~
> rv_writel
We don't hit this error and neither with i386-allyesconfig. Would be
interesting to know with which config do you get this error.
>
> Add <linux/io.h> to fix this.
Since readl and writel are used by acp3x.h, it would be better to
include linux/io.h in acp3x.h and avoid including it in every file which
includes acp3x.h
Thanks,
Akshu
prev parent reply other threads:[~2020-03-05 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 8:40 YueHaibing
2020-03-04 13:39 ` Applied "ASoc: amd: acp3x: Add missing include <linux/io.h>" to the asoc tree Mark Brown
2020-03-05 10:07 ` Agrawal, Akshu [this message]
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=5d205b07-32c4-db9e-76bb-936bca3247ce@amd.com \
--to=aagrawal2@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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®