DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/5] Fixes and supports for txgbe
Date: Thu, 29 Apr 2021 16:02:18 +0100	[thread overview]
Message-ID: <597febad-74f0-41c6-d061-321b4b7ea3dd@intel.com> (raw)
In-Reply-To: <20210429103335.23060-1-jiawenwu@trustnetic.com>

On 4/29/2021 11:33 AM, Jiawen Wu wrote:
> Fix some bugs, remove redundant code, add copyright.
> 
> v2:
> - Add a separate condition to enable and disable QINQ strip.
> - Add support for VXLAN-GPE.
> - Reword commit logs.
> - Remove redundant 'retval' variable.
> 
> Jiawen Wu (5):
>   net/txgbe: fix RSS in QINQ
>   net/txgbe: fix VF MTU limit setting
>   net/txgbe: support VXLAN-GPE
>   net/txgbe: remove port representor
>   net/txgbe: add copyright owner
> 

Except from 1/5,
Series applied to dpdk-next-net/main, thanks.

Can continue on 1/5 separately.

      parent reply	other threads:[~2021-04-29 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 10:33 Jiawen Wu
2021-04-29 10:33 ` [dpdk-dev] [PATCH v2 1/5] net/txgbe: fix RSS in QINQ Jiawen Wu
2021-04-29 14:31   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-05-06  3:33     ` Jiawen Wu
2021-04-29 10:33 ` [dpdk-dev] [PATCH v2 2/5] net/txgbe: fix VF MTU limit setting Jiawen Wu
2021-04-29 14:59   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-05-06  1:43     ` Jiawen Wu
2021-04-29 10:33 ` [dpdk-dev] [PATCH v2 3/5] net/txgbe: support VXLAN-GPE Jiawen Wu
2021-04-29 10:33 ` [dpdk-dev] [PATCH v2 4/5] net/txgbe: remove port representor Jiawen Wu
2021-04-29 10:33 ` [dpdk-dev] [PATCH v2 5/5] net/txgbe: add copyright owner Jiawen Wu
2021-04-29 14:59   ` Ferruh Yigit
2021-04-29 15:02 ` Ferruh Yigit [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=597febad-74f0-41c6-d061-321b4b7ea3dd@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiawenwu@trustnetic.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).