patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Dongdong Liu <liudongdong3@huawei.com>,
	dev@dpdk.org, thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru
Cc: stable@dpdk.org, yisen.zhuang@huawei.com, lihuisong@huawei.com
Subject: Re: [PATCH 0/6] net/hns3: some code optimization for Rx/Tx function
Date: Tue, 14 Feb 2023 11:54:49 +0000	[thread overview]
Message-ID: <67752708-ac70-237d-c05d-94888c6f7a8e@amd.com> (raw)
In-Reply-To: <20230211091830.3494-1-liudongdong3@huawei.com>

On 2/11/2023 9:18 AM, Dongdong Liu wrote:
> This patchset is to do some code optimization for Rx/Tx function.
> 
> Huisong Li (6):
>   net/hns3: fix querying dummy function failed
>   net/hns3: add debug info for Rx/Tx dummy function
>   net/hns3: remove debug condition for Tx prepare
>   net/hns3: separate tx prepare from getting Tx function
>   net/hns3: remove getting Tx function from head file
>   net/hns3: extract common functions to set Rx/Tx

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

      parent reply	other threads:[~2023-02-14 11:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  9:18 Dongdong Liu
2023-02-11  9:18 ` [PATCH 1/6] net/hns3: fix querying dummy function failed Dongdong Liu
2023-02-11  9:18 ` [PATCH 2/6] net/hns3: add debug info for Rx/Tx dummy function Dongdong Liu
2023-02-11  9:18 ` [PATCH 3/6] net/hns3: remove debug condition for Tx prepare Dongdong Liu
2023-02-11  9:18 ` [PATCH 4/6] net/hns3: separate tx prepare from getting Tx function Dongdong Liu
2023-02-11  9:18 ` [PATCH 5/6] net/hns3: remove getting Tx function from head file Dongdong Liu
2023-02-11  9:18 ` [PATCH 6/6] net/hns3: extract common functions to set Rx/Tx Dongdong Liu
2023-02-14 11:54 ` 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=67752708-ac70-237d-c05d-94888c6f7a8e@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yisen.zhuang@huawei.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).