From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ivan Malov <ivan.malov@arknetworks.am>, dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@amd.com>, Andy Moreton <amoreton@xilinx.com>
Subject: Re: [PATCH] common/sfc_efx/base: support link status change v2 events
Date: Thu, 30 Mar 2023 10:16:29 +0300 [thread overview]
Message-ID: <89267f8e-67fd-2858-44f3-d330933b7350@oktetlabs.ru> (raw)
In-Reply-To: <20230328165112.6535-1-ivan.malov@arknetworks.am>
On 3/28/23 19:51, Ivan Malov wrote:
> FW should send link status change events in either v1 or
> v2 format depending on the preference which the driver
> can express during CMD_DRV_ATTACH stage. At the moment,
> libefx does not request v2, so v1 events must arrive.
> However, FW does not honour this choice and always
> sends v2 events. So teach libefx to parse such and
> add v2 request to CMD_DRV_ATTACH, correspondingly.
>
> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2023-03-30 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:51 Ivan Malov
2023-03-30 7:16 ` Andrew Rybchenko [this message]
2023-04-07 9:24 ` Ferruh Yigit
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=89267f8e-67fd-2858-44f3-d330933b7350@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=amoreton@xilinx.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ivan.malov@arknetworks.am \
/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).