From: Kevin Traynor <ktraynor@redhat.com>
To: Hyong Youb Kim <hyonkim@cisco.com>, stable@dpdk.org
Cc: John Daley <johndale@cisco.com>
Subject: Re: [dpdk-stable] [PATCH 18.11 0/3] net/enic: a couple bug fix patches
Date: Tue, 30 Apr 2019 17:54:44 +0100 [thread overview]
Message-ID: <108d0471-ca39-2d11-383b-93a23a6a57dc@redhat.com> (raw)
In-Reply-To: <20190426070520.12375-1-hyonkim@cisco.com>
On 26/04/2019 08:05, Hyong Youb Kim wrote:
> Hi Kevin,
>
> The 2nd and 3rd patches are bug fixes that went into 19.05. They
> depend on the 1st patch, which is not a bug fix but a mechanical
> re-org. The 1st patch is also in 19.05. I hope these are acceptable to
> you. The latest 18.11 stable with these patches applied pass our
> internal tests.
>
> Thank you.
> -Hyong
>
Thanks Hyong. Pushed these into the queue and they will be pushed to
dpdk-stable next week.
> Hyong Youb Kim (3):
> net/enic: move arguments into struct
> net/enic: fix inner packet matching
> net/enic: fix VLAN inner type matching for old hardware
>
> drivers/net/enic/enic_flow.c | 564 ++++++++++++++++++++++---------------------
> 1 file changed, 290 insertions(+), 274 deletions(-)
>
prev parent reply other threads:[~2019-04-30 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 7:05 Hyong Youb Kim
2019-04-26 7:05 ` [dpdk-stable] [PATCH 18.11 1/3] net/enic: move arguments into struct Hyong Youb Kim
2019-04-26 7:05 ` [dpdk-stable] [PATCH 18.11 2/3] net/enic: fix inner packet matching Hyong Youb Kim
2019-04-26 7:05 ` [dpdk-stable] [PATCH 18.11 3/3] net/enic: fix VLAN inner type matching for old hardware Hyong Youb Kim
2019-04-30 16:54 ` Kevin Traynor [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=108d0471-ca39-2d11-383b-93a23a6a57dc@redhat.com \
--to=ktraynor@redhat.com \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).