From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ray Kinsella <mdr@ashroe.eu>
Subject: RE: [PATCH v2 1/3] common/mlx5: add Netlink event helpers
Date: Wed, 2 Mar 2022 15:56:17 +0000 [thread overview]
Message-ID: <BL1PR12MB594532AC38B95FBA358BE99CB9039@BL1PR12MB5945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <619f1f34-20d3-e4eb-e2a4-bc8208625d34@intel.com>
Hi Ferruh,
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
[...]
> Hi Dmitry,
>
> For clarification, this patch is not fix, but it is requested
> to be backported to be able to backport fixes in this patchset,
> right?
Yes.
next prev parent reply other threads:[~2022-03-02 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 16:43 [PATCH 0/3] net/mlx5: fix link state detection Dmitry Kozlyuk
2022-02-23 16:43 ` [PATCH 1/3] common/mlx5: add Netlink event helpers Dmitry Kozlyuk
2022-02-23 16:43 ` [PATCH 2/3] net/mlx5: fix link status change detection Dmitry Kozlyuk
2022-02-23 16:43 ` [PATCH 3/3] net/mlx5: fix initial link status detection Dmitry Kozlyuk
2022-03-01 12:15 ` [PATCH v2 0/3] net/mlx5: fix link state detection Dmitry Kozlyuk
2022-03-01 12:15 ` [PATCH v2 1/3] common/mlx5: add Netlink event helpers Dmitry Kozlyuk
2022-03-02 15:49 ` Ferruh Yigit
2022-03-02 15:56 ` Dmitry Kozlyuk [this message]
2022-03-08 13:48 ` Kevin Traynor
2022-03-08 15:18 ` Dmitry Kozlyuk
2022-03-01 12:15 ` [PATCH v2 2/3] net/mlx5: fix link status change detection Dmitry Kozlyuk
2022-03-01 12:15 ` [PATCH v2 3/3] net/mlx5: fix initial link status detection Dmitry Kozlyuk
2022-03-01 20:48 ` [PATCH v2 0/3] net/mlx5: fix link state detection Raslan Darawsheh
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=BL1PR12MB594532AC38B95FBA358BE99CB9039@BL1PR12MB5945.namprd12.prod.outlook.com \
--to=dkozlyuk@nvidia.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=matan@nvidia.com \
--cc=mdr@ashroe.eu \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).