From: Ian Jackson <ian.jackson@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"andy.gross@linaro.org" <andy.gross@linaro.org>,
"david.brown@linaro.org" <david.brown@linaro.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: qcom_scm: Incompatible pointer type build failure
Date: Fri, 17 May 2019 17:10:17 +0100 [thread overview]
Message-ID: <23774.56553.445601.436491@mariner.uk.xensource.com> (raw)
In-Reply-To: <87d9fbc1-5956-2b7b-0b9a-6368e378d0f6@arm.com>
Julien Grall writes ("qcom_scm: Incompatible pointer type build failure"):
> Thank you for the report.
...>
> On 30/04/2019 13:44, Ian Jackson wrote:
> > osstest service owner writes ("[linux-4.19 test] 135420: regressions - FAIL"):
> > drivers/firmware/qcom_scm.c: In function ‘qcom_scm_assign_mem’:
> > drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of ‘dma_alloc_coherent’ from incompatible pointer type [-Werror=incompatible-pointer-types]
...
> > I think this build failure is probably a regression; rather it is due
> > to the stretch update which brings in a new compiler.
>
> The bug has always been present (and still present in master), it is possible
> the compiler became smarter with the upgrade to stretch.
>
> The problem is similar to [1] and happen when the size of phys_addr_t is
> different to dma_addr_t.
>
> I have CCed the maintainers of this file.
That was several weeks ago and osstest is still blocked on this.
Can you please advise what CONFIG_* to disable to work around this ?
Ian.
WARNING: multiple messages have this Message-ID (diff)
From: Ian Jackson <ian.jackson@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"david.brown@linaro.org" <david.brown@linaro.org>,
"andy.gross@linaro.org" <andy.gross@linaro.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: qcom_scm: Incompatible pointer type build failure
Date: Fri, 17 May 2019 17:10:17 +0100 [thread overview]
Message-ID: <23774.56553.445601.436491@mariner.uk.xensource.com> (raw)
In-Reply-To: <87d9fbc1-5956-2b7b-0b9a-6368e378d0f6@arm.com>
Julien Grall writes ("qcom_scm: Incompatible pointer type build failure"):
> Thank you for the report.
...>
> On 30/04/2019 13:44, Ian Jackson wrote:
> > osstest service owner writes ("[linux-4.19 test] 135420: regressions - FAIL"):
> > drivers/firmware/qcom_scm.c: In function ‘qcom_scm_assign_mem’:
> > drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of ‘dma_alloc_coherent’ from incompatible pointer type [-Werror=incompatible-pointer-types]
...
> > I think this build failure is probably a regression; rather it is due
> > to the stretch update which brings in a new compiler.
>
> The bug has always been present (and still present in master), it is possible
> the compiler became smarter with the upgrade to stretch.
>
> The problem is similar to [1] and happen when the size of phys_addr_t is
> different to dma_addr_t.
>
> I have CCed the maintainers of this file.
That was several weeks ago and osstest is still blocked on this.
Can you please advise what CONFIG_* to disable to work around this ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Ian Jackson <ian.jackson@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"david.brown@linaro.org" <david.brown@linaro.org>,
"andy.gross@linaro.org" <andy.gross@linaro.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] qcom_scm: Incompatible pointer type build failure
Date: Fri, 17 May 2019 17:10:17 +0100 [thread overview]
Message-ID: <23774.56553.445601.436491@mariner.uk.xensource.com> (raw)
Message-ID: <20190517161017.QCu7blnD5Rjfsf6TA64SNy6_m5lNFH7szNTiMIKJbKw@z> (raw)
In-Reply-To: <87d9fbc1-5956-2b7b-0b9a-6368e378d0f6@arm.com>
Julien Grall writes ("qcom_scm: Incompatible pointer type build failure"):
> Thank you for the report.
...>
> On 30/04/2019 13:44, Ian Jackson wrote:
> > osstest service owner writes ("[linux-4.19 test] 135420: regressions - FAIL"):
> > drivers/firmware/qcom_scm.c: In function ‘qcom_scm_assign_mem’:
> > drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of ‘dma_alloc_coherent’ from incompatible pointer type [-Werror=incompatible-pointer-types]
...
> > I think this build failure is probably a regression; rather it is due
> > to the stretch update which brings in a new compiler.
>
> The bug has always been present (and still present in master), it is possible
> the compiler became smarter with the upgrade to stretch.
>
> The problem is similar to [1] and happen when the size of phys_addr_t is
> different to dma_addr_t.
>
> I have CCed the maintainers of this file.
That was several weeks ago and osstest is still blocked on this.
Can you please advise what CONFIG_* to disable to work around this ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-17 16:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 11:34 [linux-4.19 test] 135420: regressions - FAIL osstest service owner
2019-04-30 11:34 ` [Xen-devel] " osstest service owner
2019-04-30 12:44 ` linux 4.19 does not build on armhf " Ian Jackson
2019-04-30 12:44 ` [Xen-devel] " Ian Jackson
2019-04-30 14:05 ` Jan Beulich
2019-04-30 14:05 ` [Xen-devel] " Jan Beulich
2019-04-30 14:06 ` qcom_scm: Incompatible pointer type build failure Julien Grall
2019-04-30 14:06 ` Julien Grall
2019-04-30 14:06 ` [Xen-devel] " Julien Grall
2019-05-17 16:10 ` Ian Jackson [this message]
2019-05-17 16:10 ` Ian Jackson
2019-05-17 16:10 ` Ian Jackson
2019-05-17 21:09 ` [PATCH 0/3] qcom_scm: Fix some dma mapping things Stephen Boyd
2019-05-17 21:09 ` [PATCH 1/3] firmware: qcom_scm: Use proper types for dma mappings Stephen Boyd
2019-05-20 9:41 ` Ian Jackson
2019-05-20 13:20 ` Julien Grall
2019-05-30 16:51 ` [OSSTEST PATCH] ts-kernel-build: Disable CONFIG_ARCH_QCOM in Xen Project CI Ian Jackson
2019-05-30 16:51 ` [Xen-devel] " Ian Jackson
2019-05-30 16:51 ` Ian Jackson
2019-05-31 15:52 ` Julien Grall
2019-05-31 15:52 ` Julien Grall
2019-05-31 15:52 ` [Xen-devel] " Julien Grall
2019-05-17 21:09 ` [PATCH 2/3] firmware: qcom_scm: Cleanup code in qcom_scm_assign_mem() Stephen Boyd
2019-07-22 23:27 ` Bjorn Andersson
2019-07-23 0:04 ` Stephen Boyd
2019-07-23 0:21 ` Bjorn Andersson
2019-05-17 21:09 ` [PATCH 3/3] firmware: qcom_scm: Fix some typos in docs and printks Stephen Boyd
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=23774.56553.445601.436491@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=julien.grall@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.