From: Kevin Traynor <ktraynor@redhat.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>, dpdk stable <stable@dpdk.org>
Cc: "bluca@debian.org" <bluca@debian.org>,
"yskoh@mellanox.com" <yskoh@mellanox.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
"pezhang@redhat.com" <pezhang@redhat.com>
Subject: Re: [dpdk-stable] [dpdk-dev] 18.08.1 patches review and test
Date: Thu, 3 Jan 2019 13:23:34 +0000 [thread overview]
Message-ID: <8588c867-26ed-9469-048c-8eda85ce0865@redhat.com> (raw)
In-Reply-To: <1bc71a48-1d36-c73a-8485-45b2dc7bd4cc@nxp.com>
On 12/26/2018 07:31 AM, Shreyansh Jain wrote:
> Hello Kevin,
>
> I have an issue with one of the patches originating from me and targeted
> for stable. In-lined below.
>
> On Thursday 20 December 2018 05:07 PM, Kevin Traynor wrote:
>> (resend with correct subject)
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 18.08.1. Please
>> help review and test. The planned date for the final release is 16th
>> January. Before that, please shout if anyone has objections with these
>> patches being applied.
>>
>> Also for the companies committed to running regression tests,
>> please run the tests and report any issue before the release date.
>>
>> A release candidate tarball can be found at:
>>
>> https://dpdk.org/browse/dpdk-stable/tag/?id=v18.08.1-rc1
>>
>> These patches are located at branch 18.08 of dpdk-stable repo:
>> https://dpdk.org/browse/dpdk-stable/
>>
>
> [...]
>
>> Shreyansh Jain (2):
>> bus/fslmc: fix physical addressing check
>> raw/skeleton: fix memory leak on test failure <==== this
>
> Please don't apply the 'raw/skeleton: fix memory leak on test failure'
> patch. There is problem with this as reported in another patch [1]. I
Thanks Shreyansh. It was applied and pushed already, so I have reverted
it from the 18.08 stable branch.
> will push a fix out (which would actually be reverting this patch)
>
> [1] https://patches.dpdk.org/patch/48635/
>
> [...]
>
> -
> Shreyansh
>
next prev parent reply other threads:[~2019-01-03 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 11:37 [dpdk-stable] " Kevin Traynor
2018-12-26 7:31 ` [dpdk-stable] [dpdk-dev] " Shreyansh Jain
2019-01-03 13:23 ` Kevin Traynor [this message]
[not found] ` <1493197512.53622166.1545360209480.JavaMail.zimbra@redhat.com>
2019-01-08 10:47 ` [dpdk-stable] DPDK 18.08 testing - PASS //Fwd: " Sitong Liu
2019-01-30 16:27 [dpdk-stable] " Kevin Traynor
2019-03-06 16:45 ` [dpdk-stable] [dpdk-dev] " Walker, Benjamin
2019-03-06 17:36 ` Kevin Traynor
2019-03-07 11:18 ` Kevin Traynor
2019-03-22 16:56 ` Kevin Traynor
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=8588c867-26ed-9469-048c-8eda85ce0865@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).