From: Kevin Traynor <ktraynor@redhat.com>
To: Arnon Warshavsky <arnon@qwilt.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 18.11.6
Date: Wed, 11 Dec 2019 09:05:04 +0000 [thread overview]
Message-ID: <d87331f1-1e84-fe3d-cb04-c2c21c1d19c2@redhat.com> (raw)
In-Reply-To: <CAKy9EB26=OZnXeamd0W3ex9j9ymqQ4CT1tugh27e=7UO9V=EhA@mail.gmail.com>
On 11/12/2019 07:36, Arnon Warshavsky wrote:
> On Tue, Dec 3, 2019 at 9:07 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
>>
>> Can authors check your patches in the following list and either:
>> - Backport your patches to the 18.11 branch, or
>> - Indicate that the patch should not be backported
>>
>
> Hi
> Sorry for the late response.
> re
> 75dbb45f2 Arnon Warshavsky eal: fix mapping leak in secondary proces
> This patch is only relevant in the context of the rte_panic removal work
> that was not ported back.
> thanks
> /Arnon
>
Thanks Arnon, removed it from this list.
Kevin.
next prev parent reply other threads:[~2019-12-11 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191203190657.22859-1-ktraynor@redhat.com>
2019-12-04 1:57 ` Zhu, TaoX
2019-12-04 10:49 ` Kevin Traynor
2019-12-11 7:36 ` Arnon Warshavsky
2019-12-11 9:05 ` Kevin Traynor [this message]
2019-12-12 11:58 Kevin Traynor
2019-12-17 10:06 ` Somnath Kotur
2019-12-17 11:06 ` Kevin Traynor
2019-12-17 14:04 ` Kevin Traynor
2019-12-17 14:10 ` Somnath Kotur
2019-12-18 6:26 ` Somnath Kotur
2019-12-18 11:10 ` Kevin Traynor
2019-12-19 3:31 ` Somnath Kotur
-- strict thread matches above, loose matches on Subject: below --
2019-12-03 19:43 Kevin Traynor
2019-12-03 19:58 ` Kevin Traynor
2019-12-03 20:18 ` Ajit Khaparde
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=d87331f1-1e84-fe3d-cb04-c2c21c1d19c2@redhat.com \
--to=ktraynor@redhat.com \
--cc=arnon@qwilt.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).