DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stefan Puiu <stefan.puiu@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] rte_pci.h: Fix C++11 compilation
Date: Fri, 20 Feb 2015 14:22:40 +0200	[thread overview]
Message-ID: <CACKs7VB9CA7UpqtAXRjS1Xm6BbNf89b-TWeFqNqPxoMkFWr_iA@mail.gmail.com> (raw)
In-Reply-To: <2499656.ale3rhT9Ha@xps13>

Hi,

On Fri, Feb 20, 2015 at 1:26 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> Hi Stefan,
>
> Thanks for improving DPDK for C++ usage.
>
> I'm a bit lost because that's the fourth time you send the same patch (without versioning):
>         http://dpdk.org/dev/patchwork/patch/3140/
> (this one had some comments you didn't address)

Sorry. I'm new to git-send-email and to patchwork; it seems some
versions got through to patchwork but didn't make it to the list? Will
have a look at fixing the mess. And I'll address the comments :).

>         http://dpdk.org/dev/patchwork/patch/3517/
> (is it different from the first one?)
>         http://dpdk.org/dev/patchwork/patch/3518/
> (this one was wrongly formatted but authored with your ixiacom address)
>         http://dpdk.org/dev/patchwork/patch/3537/
> (it is different from the first one?)
>
> Please check http://dpdk.org/dev#send for versioning and set the old versions
> to "superseded" in patchwork.
> Thanks
>
>
> 2015-02-20 11:35, Stefan Puiu:
>>  In C++11 concatenated string literals need to have a
>>  space in between. Found with clang++-3.4, IIRC g++-4.8 also complains about this.
>>
>> Sample error message:
>> dpdk/include/rte_pci.h:96:26: error: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wreserved-user-defined-literal]
>>
>> Signed-off-by: Stefan Puiu <stefan.puiu@gmail.com>
>> ---
>>  lib/librte_eal/common/include/rte_pci.h |    4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/librte_eal/common/include/rte_pci.h b/lib/librte_eal/common/include/rte_pci.h
>> index 66ed793..12ae5a7 100644
>> --- a/lib/librte_eal/common/include/rte_pci.h
>> +++ b/lib/librte_eal/common/include/rte_pci.h
>> @@ -93,10 +93,10 @@ extern struct pci_device_list pci_device_list; /**< Global list of PCI devices.
>>  #define SYSFS_PCI_DEVICES "/sys/bus/pci/devices"
>>
>>  /** Formatting string for PCI device identifier: Ex: 0000:00:01.0 */
>> -#define PCI_PRI_FMT "%.4"PRIx16":%.2"PRIx8":%.2"PRIx8".%"PRIx8
>> +#define PCI_PRI_FMT "%.4" PRIx16 ":%.2" PRIx8 ":%.2" PRIx8 ".%" PRIx8
>>
>>  /** Short formatting string, without domain, for PCI device: Ex: 00:01.0 */
>> -#define PCI_SHORT_PRI_FMT "%.2"PRIx8":%.2"PRIx8".%"PRIx8
>> +#define PCI_SHORT_PRI_FMT "%.2" PRIx8 ":%.2" PRIx8 ".%" PRIx8
>>
>>  /** Nb. of values in PCI device identifier format string. */
>>  #define PCI_FMT_NVAL 4
>>
>
>

      reply	other threads:[~2015-02-20 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  9:35 Stefan Puiu
2015-02-20 11:26 ` Thomas Monjalon
2015-02-20 12:22   ` Stefan Puiu [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=CACKs7VB9CA7UpqtAXRjS1Xm6BbNf89b-TWeFqNqPxoMkFWr_iA@mail.gmail.com \
    --to=stefan.puiu@gmail.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).