patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Luca Boccassi <bluca@debian.org>, Shahaf Shuler <shahafs@mellanox.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 18.02] net/mlx5: add packet type index for TCP ack
Date: Mon, 23 Jul 2018 20:56:13 +0000	[thread overview]
Message-ID: <0B2600A6-51B6-488B-B462-9D1AD1BBC6F7@mellanox.com> (raw)
In-Reply-To: <1532374970.7624.13.camel@debian.org>


> On Jul 23, 2018, at 12:42 PM, Luca Boccassi <bluca@debian.org> wrote:
> 
> On Mon, 2018-07-23 at 17:31 +0000, Yongseok Koh wrote:
>> Hi, Luca
>> 
>> There's one missing patch [1] for mlx5 from master branch.
>> Please queue it for the next 18.02 stable release.
>> 
>> 
>> [1] https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit.dpdk.org%2Fdpdk%2Fcommit%2F%3Fid%3D0915e287a6a7ed884a3de198f0892&amp;data=02%7C01%7Cyskoh%40mellanox.com%7C66b7cbeafbb441a18e5708d5f0d47b0d%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636679717756380662&amp;sdata=UzAvunMfiTyjVxBRFedx92cr3iKz7jNzFKdmWsFHXGU%3D&amp;reserved=0
>> 6d8418366d4
>> 
>> Thanks,
>> Yongseok
> 
> Hi,
> 
> 18.02 is EOL as per the roadmap so in theory there shouldn't be any
> more releases: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcore.dpdk.org%2Froadmap%2F&amp;data=02%7C01%7Cyskoh%40mellanox.com%7C66b7cbeafbb441a18e5708d5f0d47b0d%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636679717756380662&amp;sdata=a9mHjfDxMgcb2paTqqJys1PNwZ1bW0k%2FrOMdjr0Suc0%3D&amp;reserved=0
> 
> How bad it is that it's missing?

Sorry, I wasn't aware of EOL. This is not a critical bug but a functional one.
I think it's okay.

Shahaf, any input?

Thanks,
Yongseok

  reply	other threads:[~2018-07-23 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 17:31 Yongseok Koh
2018-07-23 19:42 ` Luca Boccassi
2018-07-23 20:56   ` Yongseok Koh [this message]
2018-07-24  4:38     ` Shahaf Shuler

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=0B2600A6-51B6-488B-B462-9D1AD1BBC6F7@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=bluca@debian.org \
    --cc=shahafs@mellanox.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).