From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] net/bonding: rename bonded to bonding
Date: Fri, 2 Jun 2023 16:15:04 +0100 [thread overview]
Message-ID: <73a62e38-aed8-579c-4d3d-3ded682e1f4a@amd.com> (raw)
In-Reply-To: <20230524071204.2484248-1-chaoyong.he@corigine.com>
On 5/24/2023 8:12 AM, Chaoyong He wrote:
> From: Long Wu <long.wu@corigine.com>
>
> DPDK bonding PMD mixing use 'bonded' and 'bonding' currently, this
> patch replaces the usage of the word 'bonded' with more appropriate
> word 'bonding' in bonding PMD and ethdev library as well as in
> their docs. Also the test app and testpmd were modified to use the
> new wording.
>
> In addition to grammar requirements, we should still use bonded,
> and in other cases, we should use bonding.
>
> Signed-off-by: Long Wu <long.wu@corigine.com>
> ---
> Depends-on: patch-1531512 ("[v4] net/bonding: replace master/slave to")
>
'Depends-on' should have patchwork patch/patchset number, above number
is part of message id, so it is not useful to find referenced patch, it
should be:
Depends-on: patch-126979
(https://dpdk.org/patch/126979)
The dependent patch is deferred to next release, v23.11, so need to
defer this patch too.
Or if there is a target/reason to have this patch in this release, you
can make a new version on top of current next-net head and send a new
version, up to you.
For now I am assuming we will continue with this patch and I defer it.
next prev parent reply other threads:[~2023-06-02 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 7:12 Chaoyong He
2023-05-24 14:48 ` Stephen Hemminger
2023-06-02 15:15 ` Ferruh Yigit [this message]
2023-06-02 17:04 ` Ferruh Yigit
2023-09-21 6:10 ` [PATCH v2] " Chaoyong He
2023-09-21 10:11 ` 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=73a62e38-aed8-579c-4d3d-3ded682e1f4a@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=long.wu@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).