From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, Jie Zhou <jizh@microsoft.com>,
Ranjit Menon <ranjit.menon@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Ori Kam <orika@nvidia.com>, Radu Nicolau <radu.nicolau@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Jasvinder Singh <jasvinder.singh@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
David Hunt <david.hunt@intel.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3] cmdline: avoid name clash with Windows system types
Date: Thu, 05 Nov 2020 17:50:25 +0100 [thread overview]
Message-ID: <2058307.rIv2Fu1MPt@thomas> (raw)
In-Reply-To: <20201105133130.GT1898@platinum>
05/11/2020 14:31, Olivier Matz:
> On Fri, Oct 30, 2020 at 04:01:26AM +0300, Dmitry Kozlyuk wrote:
> > cmdline_numtype member names clash with Windows system identifiers.
> > Add RTE_ prefix to cmdline constants to avoid this and possible
> > future conflicts.
> >
> > Suggested-by: Ranjit Menon <ranjit.menon@intel.com>
> > Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
Applied, thanks
prev parent reply other threads:[~2020-11-05 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 18:48 [dpdk-dev] [PATCH] cmdline: avoid name clash with Windows system types Dmitry Kozlyuk
2020-08-21 20:58 ` Jie Zhou
2020-08-22 0:43 ` Ranjit Menon
2020-09-02 18:38 ` [dpdk-dev] [PATCH v2] " Dmitry Kozlyuk
2020-09-03 9:20 ` Bruce Richardson
2020-09-03 9:30 ` Dmitry Kozlyuk
2020-09-03 9:40 ` Bruce Richardson
2020-09-17 14:15 ` Olivier Matz
2020-10-30 1:01 ` [dpdk-dev] [PATCH v3] " Dmitry Kozlyuk
2020-10-30 21:20 ` Ranjit Menon
2020-10-31 0:00 ` Jie Zhou
2020-11-05 13:31 ` Olivier Matz
2020-11-05 16:50 ` 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=2058307.rIv2Fu1MPt@thomas \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=chenbo.xia@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=jasvinder.singh@intel.com \
--cc=jizh@microsoft.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=orika@nvidia.com \
--cc=radu.nicolau@intel.com \
--cc=ranjit.menon@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.