DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3] bus/fslmc: use PRIu64 instead of llX in format specifier
Date: Sun, 15 Apr 2018 14:22:01 +0200	[thread overview]
Message-ID: <1762360.39Q5AbQuW3@xps> (raw)
In-Reply-To: <4365a1c7-b752-0872-f220-10b50be3bce5@nxp.com>

13/04/2018 14:44, Hemant Agrawal:
> 
> On 4/13/2018 4:52 PM, 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>
> > --
> > v3:
> >   - correction to prefix address with 0x
> > v2:
> >   - corrected format specifier wrt address and size.
> >     Thanks Shreyansh, Hemant and Thomas.
> > 
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Applied, thanks

      reply	other threads:[~2018-04-15 12:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  5:04 [dpdk-dev] [PATCH] " Gowrishankar
2018-04-13  7:10 ` Shreyansh Jain
2018-04-13  7:09   ` Hemant Agrawal
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 [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=1762360.39Q5AbQuW3@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gowrishankar.m@linux.vnet.ibm.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=shreyansh.jain@nxp.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).