From: Thierry Reding <thierry.reding@gmail.com>
To: Emil Goode <emil.fsw@goode.io>
Cc: Thierry Reding <treding@nvidia.com>,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] gpu: host1x: Fix compiler errors
Date: Mon, 26 Mar 2018 16:57:34 +0200 [thread overview]
Message-ID: <20180326145734.GA8016@ulmo> (raw)
In-Reply-To: <20180326144314.xeuocqp5fjpfjm3q@lianli>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
On Mon, Mar 26, 2018 at 04:44:14PM +0200, Emil Goode wrote:
> The compiler is complaining with the following errors:
>
> drivers/gpu/host1x/cdma.c:94:48: error:
> passing argument 3 of ‘dma_alloc_wc’ from incompatible pointer type
> [-Werror=incompatible-pointer-types]
>
> drivers/gpu/host1x/cdma.c:113:48: error:
> passing argument 3 of ‘dma_alloc_wc’ from incompatible pointer type
> [-Werror=incompatible-pointer-types]
>
> The expected pointer type of the third argument to dma_alloc_wc() is
> dma_addr_t but phys_addr_t is passed. Fix this by adding casts to the
> expected pointer type.
>
> Signed-off-by: Emil Goode <emil.fsw@goode.io>
> ---
> drivers/gpu/host1x/cdma.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
What compiler do you use? I do regular builds and check for warnings and
errors, and this one is new to me.
Thierry
>
> diff --git a/drivers/gpu/host1x/cdma.c b/drivers/gpu/host1x/cdma.c
> index 28541b280739..5e8b321a751e 100644
> --- a/drivers/gpu/host1x/cdma.c
> +++ b/drivers/gpu/host1x/cdma.c
> @@ -91,8 +91,8 @@ static int host1x_pushbuffer_init(struct push_buffer *pb)
>
> size = iova_align(&host1x->iova, size);
>
> - pb->mapped = dma_alloc_wc(host1x->dev, size, &pb->phys,
> - GFP_KERNEL);
> + pb->mapped = dma_alloc_wc(host1x->dev, size,
> + (dma_addr_t *)&pb->phys, GFP_KERNEL);
> if (!pb->mapped)
> return -ENOMEM;
>
> @@ -110,8 +110,8 @@ static int host1x_pushbuffer_init(struct push_buffer *pb)
> if (err)
> goto iommu_free_iova;
> } else {
> - pb->mapped = dma_alloc_wc(host1x->dev, size, &pb->phys,
> - GFP_KERNEL);
> + pb->mapped = dma_alloc_wc(host1x->dev, size,
> + (dma_addr_t *)&pb->phys, GFP_KERNEL);
> if (!pb->mapped)
> return -ENOMEM;
>
> --
> 2.11.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-26 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 14:44 [PATCH] gpu: host1x: Fix compiler errors Emil Goode
2018-03-26 14:57 ` Thierry Reding [this message]
2018-03-26 15:47 ` Emil Goode
2018-05-14 8:43 ` Thierry Reding
2018-05-15 21:07 ` Emil Goode
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=20180326145734.GA8016@ulmo \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.fsw@goode.io \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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