DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maayan Kashani <mkashani@nvidia.com>
To: Yogev Chaimovich <yogev@cgstowernetworks.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/mlx5: fix transceiver warning when not exist
Date: Tue, 10 Jun 2025 05:47:04 +0000	[thread overview]
Message-ID: <SA1PR12MB70378DE7BBC81189B4899E20B26AA@SA1PR12MB7037.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DU2PR09MB54860A76C9E7A1CFF4A00AF0D66BA@DU2PR09MB5486.eurprd09.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3707 bytes --]

Sometimes it’s just a failure in the testing system and needs to retrigger the tests.

Regards,
Maayan Kashani

From: Yogev Chaimovich <yogev@cgstowernetworks.com>
Sent: Monday, 9 June 2025 16:11
To: Maayan Kashani <mkashani@nvidia.com>; Stephen Hemminger <stephen@networkplumber.org>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Bing Zhao <bingz@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Matan Azrad <matan@nvidia.com>; dev@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix transceiver warning when not exist

External email: Use caution opening links or attachments

Hi,
Actually looks like we're going with another workaround, so I might not be needing my original patch.
Also, I do not understand how my patch (not printing a log) makes a test fail - I couldn't find that test in DPDK to verify. I'm not that familiar though..

Yogev
________________________________
From: Maayan Kashani <mkashani@nvidia.com<mailto:mkashani@nvidia.com>>
Sent: Wednesday, June 4, 2025 10:02
To: Stephen Hemminger <stephen@networkplumber.org<mailto:stephen@networkplumber.org>>; Yogev Chaimovich <yogev@cgstowernetworks.com<mailto:yogev@cgstowernetworks.com>>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com<mailto:dsosnowski@nvidia.com>>; Slava Ovsiienko <viacheslavo@nvidia.com<mailto:viacheslavo@nvidia.com>>; Bing Zhao <bingz@nvidia.com<mailto:bingz@nvidia.com>>; Ori Kam <orika@nvidia.com<mailto:orika@nvidia.com>>; Suanming Mou <suanmingm@nvidia.com<mailto:suanmingm@nvidia.com>>; Matan Azrad <matan@nvidia.com<mailto:matan@nvidia.com>>; dev@dpdk.org<mailto:dev@dpdk.org> <dev@dpdk.org<mailto:dev@dpdk.org>>
Subject: RE: [PATCH] net/mlx5: fix transceiver warning when not exist

Hi, Yogev,
Thank you for contributing,
Can you fix the failing CI TEST?
https://patches.dpdk.org/project/dpdk/patch/20250506133107.4432-1-yogev@cgstowernetworks.com/

Regards,
Maayan Kashani

> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org<mailto:stephen@networkplumber.org>>
> Sent: Tuesday, 20 May 2025 21:49
> To: Yogev Chaimovich <yogev@cgstowernetworks.com<mailto:yogev@cgstowernetworks.com>>
> Cc: Dariusz Sosnowski <dsosnowski@nvidia.com<mailto:dsosnowski@nvidia.com>>; Slava Ovsiienko
> <viacheslavo@nvidia.com<mailto:viacheslavo@nvidia.com>>; Bing Zhao <bingz@nvidia.com<mailto:bingz@nvidia.com>>; Ori Kam
> <orika@nvidia.com<mailto:orika@nvidia.com>>; Suanming Mou <suanmingm@nvidia.com<mailto:suanmingm@nvidia.com>>; Matan
> Azrad <matan@nvidia.com<mailto:matan@nvidia.com>>; dev@dpdk.org<mailto:dev@dpdk.org>
> Subject: Re: [PATCH] net/mlx5: fix transceiver warning when not exist
>
> External email: Use caution opening links or attachments
>
>
> On Mon, 5 May 2025 12:14:51 +0000
> Yogev Chaimovich <yogev@cgstowernetworks.com<mailto:yogev@cgstowernetworks.com>> wrote:
>
> > From ffe666291bc531b89620cc28a7b45fa209700f35 Mon Sep 17 00:00:00
> 2001
> > From: yogev <yogev@cgstowernetworks.com<mailto:yogev@cgstowernetworks.com>>
> > Date: Sun, 4 May 2025 23:11:46 +0300
> > Subject: [PATCH] net/mlx5: fix transceiver warning when not exist
> >
> > In case no transceiver exist when trying to get the transceiver's info
> > There should not be an error message from the library.
> > The caller may print an appropriate error message using the relevant
> rte_errno if required.
> >
> > Signed-off-by: yogev <yogev@cgstowernetworks.com<mailto:yogev@cgstowernetworks.com>>
>
> Signed off by is a legal requirement and must use your full name.
> As in:
>    Signed-off-by: Yogev Chaimovich <yogev@cgstowernetworks.com<mailto:yogev@cgstowernetworks.com>>

[-- Attachment #2: Type: text/html, Size: 9071 bytes --]

  reply	other threads:[~2025-06-10  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 12:14 Yogev Chaimovich
2025-05-20 18:49 ` Stephen Hemminger
2025-06-04  7:02   ` Maayan Kashani
2025-06-09 13:11     ` Yogev Chaimovich
2025-06-10  5:47       ` Maayan Kashani [this message]
2025-05-06 13:31 yogev

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=SA1PR12MB70378DE7BBC81189B4899E20B26AA@SA1PR12MB7037.namprd12.prod.outlook.com \
    --to=mkashani@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stephen@networkplumber.org \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.com \
    --cc=yogev@cgstowernetworks.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).