From: Stephen Hemminger <stephen@networkplumber.org>
To: Yang Xu <xu.yang3@zte.com.cn>
Cc: thomas@monjalon.net, dsosnowski@nvidia.com,
viacheslavo@nvidia.com, bingz@nvidia.com, orika@nvidia.com,
suanmingm@nvidia.com, matan@nvidia.com, yao.chenghu@zte.com.cn,
dev@dpdk.org
Subject: Re: [PATCH v2 1/1] net/mlx5: fix set port down if detect anomaly
Date: Mon, 17 Nov 2025 10:01:23 -0800 [thread overview]
Message-ID: <20251117100123.3cdbb741@phoenix> (raw)
In-Reply-To: <20251117091201.2261526-1-xu.yang3@zte.com.cn>
On Mon, 17 Nov 2025 17:12:01 +0800
Yang Xu <xu.yang3@zte.com.cn> wrote:
> diff --git a/test.eml b/test.eml
> new file mode 100644
> index 0000000000..f30ef5dc8a
> --- /dev/null
> +++ b/test.eml
> @@ -0,0 +1,21 @@
> +./../dpdk-patch/0001-net-mlx5-fix-set-port-down-if-detect-anomaly.patch
> +(mbox) Adding cc: Yang Xu <xu.yang3@zte.com.cn> from line 'From: Yang Xu <xu.yang3@zte.com.cn>'
> +(body) Adding cc: Yang Xu <xu.yang3@zte.com.cn> from line 'Signed-off-by: Yang Xu <xu.yang3@zte.com.cn>'
> +Dry-OK. Log says:
> +Server: 10.5.231.43
> +MAIL FROM:<xu.yang3@zte.com.cn>
> +RCPT TO:<y>
> +RCPT TO:<xu.yang3@zte.com.cn>
> +From: Yang Xu <xu.yang3@zte.com.cn>
> +To: y
> +Cc: Yang Xu <xu.yang3@zte.com.cn>
> +Subject: [PATCH v2 1/1] net/mlx5: fix set port down if detect anomaly
> +Date: Fri, 14 Nov 2025 10:14:11 +0800
> +Message-Id: <20251114021411.3606817-1-xu.yang3@zte.com.cn>
> +X-Mailer: git-send-email 2.27.0
> +In-Reply-To: <y>
> +References: <y>
> +MIME-Version: 1.0
> +Content-Transfer-Encoding: 8bit
> +
> +Result: OK
> --
Bogus file, should not be in patch submission
prev parent reply other threads:[~2025-11-17 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 9:12 [PATCH v2 1/1] net/mlx5: fix set port down if detect anomaly Yang Xu
2025-11-17 9:37 ` Bing Zhao
2025-11-17 18:01 ` Stephen Hemminger [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=20251117100123.3cdbb741@phoenix \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=xu.yang3@zte.com.cn \
--cc=yao.chenghu@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.