DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] net/enic: minor updates
Date: Wed, 12 Jun 2019 14:28:24 +0100	[thread overview]
Message-ID: <6651b506-2f2f-8bfb-21e9-f25abad1387f@intel.com> (raw)
In-Reply-To: <20190606152658.17311-1-hyonkim@cisco.com>

On 6/6/2019 4:26 PM, Hyong Youb Kim wrote:
> The first two patches report the min/max MTU and speed capabilities to
> support applications that rely on them. The other two patches remove
> unnecessary/unsupported code from the flow implementation. We do not
> expect more patches for 19.08.
> 
> Hyong Youb Kim (2):
>   net/enic: set min and max MTU
>   net/enic: report speed capabilities
> 
> John Daley (2):
>   net/enic: remove support for flow count action
>   net/enic: remove locks from rte flow code

Series applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2019-06-12 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 15:26 Hyong Youb Kim
2019-06-06 15:26 ` [dpdk-dev] [PATCH 1/4] net/enic: set min and max MTU Hyong Youb Kim
2019-06-06 15:26 ` [dpdk-dev] [PATCH 2/4] net/enic: report speed capabilities Hyong Youb Kim
2019-06-06 15:26 ` [dpdk-dev] [PATCH 3/4] net/enic: remove support for flow count action Hyong Youb Kim
2019-06-06 15:26 ` [dpdk-dev] [PATCH 4/4] net/enic: remove locks from rte flow code Hyong Youb Kim
2019-06-12 13:28 ` Ferruh Yigit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-10 18:28 [dpdk-dev] [PATCH 0/4] net/enic: minor updates Hyong Youb Kim
2018-12-12 11:56 ` Ferruh Yigit

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=6651b506-2f2f-8bfb-21e9-f25abad1387f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=hyonkim@cisco.com \
    --cc=johndale@cisco.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).