patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>, 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: Tue, 8 Mar 2022 13:48:28 +0000	[thread overview]
Message-ID: <d579e205-3ae7-011d-3a76-90f13617a7f2@redhat.com> (raw)
In-Reply-To: <BL1PR12MB594532AC38B95FBA358BE99CB9039@BL1PR12MB5945.namprd12.prod.outlook.com>

On 02/03/2022 15:56, Dmitry Kozlyuk wrote:
> 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.

The updated API is internal so that should be ok. I'm ok to take this on 
21.11 as long as you can confirm it's not breaking any user 
compatibility with external sw versions/ABI/API etc from 21.11.0 ?

Assuming that's ok, please send a rebased series for 21.11. I'm not 
comfortable rebasing the series with the amount of changes on dpdk main 
branch to same functions in mlx5_os.c.

P.S. Better to rebase on patch queue [0] to avoid conflicts with other 
backports not pushed to dpdk.org yet.

thanks,
Kevin.

[0] https://github.com/kevintraynor/dpdk-stable.git


  reply	other threads:[~2022-03-08 13:48 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
2022-03-02 15:56       ` Dmitry Kozlyuk
2022-03-08 13:48         ` Kevin Traynor [this message]
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=d579e205-3ae7-011d-3a76-90f13617a7f2@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=dkozlyuk@nvidia.com \
    --cc=ferruh.yigit@intel.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).