From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Luca Boccassi <bluca@debian.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] Please help fixing ARM64 on 18.02 stable branch
Date: Mon, 21 May 2018 10:01:49 +0000 [thread overview]
Message-ID: <HE1PR0402MB2780C2923B9C6687826A016090950@HE1PR0402MB2780.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1526896785.23337.145.camel@debian.org>
Hello Luca,
Can you confirm the compiler and the output you are getting?
Meanwhile, I will get the environment ready.
-
Shreyansh
> -----Original Message-----
> From: Luca Boccassi [mailto:bluca@debian.org]
> Sent: Monday, May 21, 2018 3:30 PM
> To: Hemant Agrawal <hemant.agrawal@nxp.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>
> Cc: thomas@monjalon.net; stable@dpdk.org
> Subject: Please help fixing ARM64 on 18.02 stable branch
>
> Hello,
>
> Thomas found a build error in the DPAA2 PMD when cross-building to
> arm64, if you can could you please help us and provide a fix for the
> 18.02 stable branch?
>
> As a reminder, you can clone the 18.02 branch from the dpdk-stable
> tree:
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpdk
> .org%2Fbrowse%2Fdpdk-
> stable%2F&data=02%7C01%7Cshreyansh.jain%40nxp.com%7Ca73874f1467648c0a39
> 308d5bf01960b%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636624935951
> 970166&sdata=N2fS0havgeNF4qHlClqlOXx0fIiPkW9r4BHUnUarSO0%3D&reserved=0
>
> Thanks!
>
> --
> Kind regards,
> Luca Boccassi
next prev parent reply other threads:[~2018-05-21 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 9:59 Luca Boccassi
2018-05-21 10:01 ` Shreyansh Jain [this message]
2018-05-21 10:11 ` Thomas Monjalon
2018-05-21 13:03 ` Shreyansh Jain
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=HE1PR0402MB2780C2923B9C6687826A016090950@HE1PR0402MB2780.eurprd04.prod.outlook.com \
--to=shreyansh.jain@nxp.com \
--cc=bluca@debian.org \
--cc=hemant.agrawal@nxp.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).