patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>, <dev@dpdk.org>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Cc: <stable@dpdk.org>, Viacheslav 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:49:35 +0000	[thread overview]
Message-ID: <619f1f34-20d3-e4eb-e2a4-bc8208625d34@intel.com> (raw)
In-Reply-To: <20220301121514.41497-2-dkozlyuk@nvidia.com>

On 3/1/2022 12:15 PM, Dmitry Kozlyuk wrote:
> Introduce mlx5_nl_read_events() to read Netlink events
> (technically, messages) from a socket that was configured
> to listen for them via a new mlx5_nl_init() parameter.
> Add mlx5_nl_parse_link_status_update() helper
> to extract information from link-related events.
> This patch is a shared base for later fixes.
> 
> Cc: stable@dpdk.org
> 

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?

This looks OK to me, but cc'ed LTS maintainers in case they
have objection.

> Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
> Reviewed-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>


<...>

  reply	other threads:[~2022-03-02 15:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220223164333.3834590-1-dkozlyuk@nvidia.com>
2022-02-23 16:43 ` [PATCH " 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
     [not found] ` <20220301121514.41497-1-dkozlyuk@nvidia.com>
2022-03-01 12:15   ` [PATCH v2 1/3] common/mlx5: add Netlink event helpers Dmitry Kozlyuk
2022-03-02 15:49     ` Ferruh Yigit [this message]
2022-03-02 15:56       ` Dmitry Kozlyuk
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

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=619f1f34-20d3-e4eb-e2a4-bc8208625d34@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=dkozlyuk@nvidia.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).