patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
	"Lipiec, Herakliusz" <herakliusz.lipiec@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] app/testpmd: fix printf format specifiers
Date: Thu, 11 Oct 2018 12:20:46 +0100	[thread overview]
Message-ID: <b217e882-13ed-c276-be51-c27c7b25446d@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260CF478B@IRSMSX107.ger.corp.intel.com>

On 9/25/2018 5:00 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: Lipiec, Herakliusz
>> Sent: Tuesday, September 25, 2018 12:23 PM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
>> <jingjing.wu@intel.com>; Iremonger, Bernard
>> <bernard.iremonger@intel.com>
>> Cc: dev@dpdk.org; Lipiec, Herakliusz <herakliusz.lipiec@intel.com>;
>> stable@dpdk.org
>> Subject: [PATCH v2] app/testpmd: fix printf format specifiers
>>
>> change PRIu8 -> PRIu16 for port_id in eth_event_callback (portid_t is
>> uint16_t)
>>
>> Fixes: 76ad4a2d82d4 ("app/testpmd: add generic event handler")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
> 
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2018-10-11 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 15:49 [dpdk-stable] [PATCH] " Herakliusz Lipiec
2018-09-25 11:23 ` [dpdk-stable] [PATCH v2] " Herakliusz Lipiec
2018-09-25 16:00   ` Iremonger, Bernard
2018-10-11 11:20     ` Ferruh Yigit [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=b217e882-13ed-c276-be51-c27c7b25446d@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=herakliusz.lipiec@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@intel.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).