From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>,
Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] bus/fslmc: use PRIu64 instead of llX in format specifier
Date: Fri, 13 Apr 2018 12:39:16 +0530 [thread overview]
Message-ID: <1ad8c1f3-e92a-5e71-30f9-90a53f45bd1c@nxp.com> (raw)
In-Reply-To: <778ed616-ee7b-6fec-53f1-bb112f0100bd@nxp.com>
On 4/13/2018 12:40 PM, Shreyansh Jain wrote:
> On Friday 13 April 2018 10:34 AM, Gowrishankar wrote:
>> From: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
>>
>> Instead of llX, use C99 standard "PRIu64" in format specifier. Former one
>> breaks compile in ppc64le.
>>
>> Fixes: c2c167fdb3 ("bus/fslmc: support memory event callbacks for VFIO")
>>
>> Signed-off-by: Gowrishankar Muthukrishnan
>> <gowrishankar.m@linux.vnet.ibm.com>
>> --
>
> Thanks for fixing.
>
> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
NACK
This is breaking the x86_64-native-linuxapp-gcc compilation. I am
looking into it.
next prev parent reply other threads:[~2018-04-13 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 5:04 Gowrishankar
2018-04-13 7:10 ` Shreyansh Jain
2018-04-13 7:09 ` Hemant Agrawal [this message]
2018-04-13 7:37 ` Hemant Agrawal
2018-04-13 7:41 ` Thomas Monjalon
2018-04-13 8:56 ` Shreyansh Jain
2018-04-13 8:43 ` gowrishankar muthukrishnan
2018-04-13 10:37 ` Shreyansh Jain
2018-04-13 10:40 ` [dpdk-dev] [PATCH v2] " Gowrishankar
2018-04-13 10:47 ` gowrishankar muthukrishnan
2018-04-13 10:55 ` Gowrishankar
2018-04-13 11:17 ` Shreyansh Jain
2018-04-13 11:22 ` [dpdk-dev] [PATCH v3] " Gowrishankar
2018-04-13 12:44 ` Hemant Agrawal
2018-04-15 12:22 ` Thomas Monjalon
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=1ad8c1f3-e92a-5e71-30f9-90a53f45bd1c@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=shreyansh.jain@nxp.com \
--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).