From: Thomas Monjalon <thomas@monjalon.net>
To: Ophir Munk <ophirmu@nvidia.com>
Cc: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>,
Ori Kam <orika@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] app/regex: fix segfault in getopt_long call
Date: Tue, 20 Oct 2020 00:05:08 +0200 [thread overview]
Message-ID: <2682030.zKVDcF2K60@thomas> (raw)
In-Reply-To: <DM5PR12MB116175A99E0C59D2C4309577DC1E0@DM5PR12MB1161.namprd12.prod.outlook.com>
19/10/2020 10:39, Ophir Munk:
> Adding Thomas Monjalon
> Thomas - when merging can you please remove the line: Cc: stable@dpdk.org ?
No it should be kept because the bug is in a previous release.
next prev parent reply other threads:[~2020-10-19 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 14:21 Ophir Munk
2020-10-19 7:46 ` Ori Kam
2020-10-19 8:13 ` Lukasz Wojciechowski
2020-10-19 8:39 ` Ophir Munk
2020-10-19 22:05 ` Thomas Monjalon [this message]
2020-10-19 22:06 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
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=2682030.zKVDcF2K60@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=l.wojciechow@partner.samsung.com \
--cc=ophirmu@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
/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).