From: "Min Hu (Connor)" <humin29@huawei.com>
To: <grive@u256.net>
Cc: <chas3@att.com>, <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev][PATCH v1, 1/2] bonding: fix port id validity check on parsing
Date: Thu, 26 Nov 2020 10:45:45 +0800 [thread overview]
Message-ID: <1606358745-38884-1-git-send-email-humin29@huawei.com> (raw)
In-Reply-To: <0d0871d076871a3c7d9ea0d2dc479a725151f8c0.1587137703.git.grive@u256.net>
It looks good to me, thanks.
next prev parent reply other threads:[~2020-11-26 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1587137703.git.grive@u256.net>
2020-04-17 16:42 ` [dpdk-stable] [PATCH v1 " Gaetan Rivet
2020-11-26 2:45 ` Min Hu (Connor) [this message]
2020-12-07 13:34 ` [dpdk-stable] [dpdk-dev] [PATCH v1, " Ferruh Yigit
2020-04-17 16:42 ` [dpdk-stable] [PATCH v1 2/2] bonding: fix PCI address comparison on non-pci ports Gaetan Rivet
2020-11-26 2:24 ` [dpdk-stable] [v1, " Min Hu (Connor)
2020-12-07 14:07 ` Gaëtan Rivet
2020-12-16 12:14 ` Min Hu (Connor)
2020-12-17 10:53 ` 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=1606358745-38884-1-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--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).