From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] Headers: more C++11 compilation fixes
Date: Tue, 24 Feb 2015 02:49:52 +0100 [thread overview]
Message-ID: <3433744.1z45dPKCim@xps13> (raw)
In-Reply-To: <1424438606-1130-2-git-send-email-stefan.puiu@gmail.com>
2015-02-20 15:23, Stefan Puiu:
> Fixed two more places where non-C++11 string concatenation is
> used. Spotted by John McNamara.
>
> Signed-off-by: Stefan Puiu <stefan.puiu@gmail.com>
Both patches merged and applied, thanks.
prev parent reply other threads:[~2015-02-24 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 8:50 [dpdk-dev] [PATCH] Minor C++11 compilation fix for rte_pci.h Stefan Puiu
2015-02-13 8:25 ` Mcnamara, John
2015-02-13 10:17 ` Bruce Richardson
2015-02-13 10:27 ` Mcnamara, John
2015-02-20 12:26 ` Stefan Puiu
2015-02-20 13:18 ` [dpdk-dev] [PATCH 1/2] rte_pci.h: Fix C++11 compilation Stefan Puiu
2015-02-20 13:23 ` Stefan Puiu
2015-02-20 13:23 ` [dpdk-dev] [PATCH 2/2] Headers: more C++11 compilation fixes Stefan Puiu
2015-02-24 1:49 ` 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=3433744.1z45dPKCim@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stefan.puiu@gmail.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).