From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "kirill.rybalchenko@intel.com" <kirill.rybalchenko@intel.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] bus/fslmc: add QBMAN driver to bus patch problem
Date: Tue, 17 Apr 2018 12:20:41 +0000 [thread overview]
Message-ID: <AM2PR04MB0753C1B4FDC2AB996B749DA789B70@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1b1fb4b6-2656-b4de-602f-a4dc5efd0a1c@redhat.com>
I missed it. We will check it asap.
Sent from my Android phone using TouchDown (www.symantec.com)
-----Original Message-----
From: Maxime Coquelin [maxime.coquelin@redhat.com]
Received: Tuesday, 17 Apr 2018, 5:43PM
To: Rybalchenko, Kirill [kirill.rybalchenko@intel.com]; Hemant Agrawal [hemant.agrawal@nxp.com]
CC: dev@dpdk.org [dev@dpdk.org]
Subject: Re: [dpdk-dev] bus/fslmc: add QBMAN driver to bus patch problem
Hi Hemant
On 03/29/2018 01:48 PM, Rybalchenko, Kirill wrote:
> Hello Hemant,
> I found that a number of patches submitted for 18.05 release fail in compilation:
>
> Failed Build #1:
> OS: CentOS7_64
> Target: x86_64-native-linuxapp-clang
> In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_portal.c:7:
> In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_portal.h:7:
> In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_sys.h:21:
> In file included from /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/qbman_sys_decl.h:7:
> /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/include/fsl_qbman_base.h:9:19: error: redefinition of typedef 'dma_addr_t' is a C11 feature [-Werror,-Wtypedef-redefinition]
> typedef uint64_t dma_addr_t;
> ^
> /home/patchWorkOrg/compilation/drivers/bus/fslmc/qbman/include/compat.h:35:18: note: previous definition is here
> typedef uint64_t dma_addr_t;
>
> This failure caused by patch "bus/fslmc: add QBMAN driver to bus"
> commit
> 531b17a780dc5f486e8be8d82d1ccd077ea25f14
> from Apr 11 2017
>
> Could you please have a look to your patch?
Did you find time to have a look at it?
It breaks automated clang builds, so this is quite annoying.
My clang version:
clang version 3.4.2 (tags/RELEASE_34/dot2-final)
Thanks in advance,
Maxime
> Thanks,
> Kirill Rybalchenko.
>
>
prev parent reply other threads:[~2018-04-17 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 11:48 Rybalchenko, Kirill
2018-04-17 12:13 ` Maxime Coquelin
2018-04-17 12:20 ` Hemant Agrawal [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=AM2PR04MB0753C1B4FDC2AB996B749DA789B70@AM2PR04MB0753.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=kirill.rybalchenko@intel.com \
--cc=maxime.coquelin@redhat.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;
as well as URLs for NNTP newsgroup(s).