From: Ivan Malov <ivan.malov@arknetworks.am>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Andy Moreton <andy.moreton@amd.com>,
Pieter Jansen Van Vuuren <pieter.jansen-van-vuuren@amd.com>,
Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>,
dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 1/9] doc: remove support for AMD Solarflare SFN7xxx family boards
Date: Mon, 2 Feb 2026 18:05:22 +0400 (+04) [thread overview]
Message-ID: <ebd63f2d-0a71-7774-d0c1-d2ee3405c4fd@arknetworks.am> (raw)
In-Reply-To: <5939885.GXAFRqVoOG@thomas>
Hi Thomas,
Apologies for being late with response.
On Mon, 2 Feb 2026, Thomas Monjalon wrote:
> 01/02/2026 21:17, Thomas Monjalon:
>> 29/12/2025 22:35, Ivan Malov:
>>> +* **Removed support for AMD Solarflare SFN7xxx family boards.**
>>> +
>>> + 7000 series adaptors are out of support in terms of hardware.
>>
>> Just to be clear, it is only a doc change?
>> The code still works for this hardware?
>
> Please, may I have an answer?
> I cannot merge into main that you remove something if it's only in doc.
> It is blocking, I want a clearer message to merge please.
The code is still functional. However, the situation is a bit more nuanced.
In fact, the fix contained in the series is supposed to make the driver
work properly on late Medford2 adapters, but for early devices, like
SFN7xxx, this fix might cause issues with flow control. Hence the
doc message. I think it serves some valid informative purpose.
Thank you.
>
>
>
next prev parent reply other threads:[~2026-02-02 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 21:35 [PATCH 0/9] net/sfc: SFN7xxx deprecation and Medford fixes Ivan Malov
2025-12-29 21:35 ` [PATCH 1/9] doc: remove support for AMD Solarflare SFN7xxx family boards Ivan Malov
2026-02-01 20:17 ` Thomas Monjalon
2026-02-02 13:51 ` Thomas Monjalon
2026-02-02 14:05 ` Ivan Malov [this message]
2026-02-02 16:31 ` Thomas Monjalon
2026-02-02 16:38 ` Ivan Malov
2026-02-02 17:06 ` Thomas Monjalon
2025-12-29 21:35 ` [PATCH 2/9] common/sfc_efx/base: fix flow control setting on legacy MCDI Ivan Malov
2025-12-29 21:35 ` [PATCH 3/9] common/sfc_efx/base: fix indication of requestable FEC flags Ivan Malov
2025-12-29 21:35 ` [PATCH 4/9] common/sfc_efx/base: define mask for pause mode capabilities Ivan Malov
2025-12-29 21:35 ` [PATCH 5/9] common/sfc_efx/base: count Rx TRUNC ERR as CRC errors on X4 Ivan Malov
2025-12-29 21:35 ` [PATCH 6/9] net/sfc: avoid speed reset when setting FEC in started state Ivan Malov
2025-12-29 21:35 ` [PATCH 7/9] net/sfc: rework the capability check that is done on FEC set Ivan Malov
2025-12-29 21:35 ` [PATCH 8/9] net/sfc: drop AUTO from FEC capabilities and fix the comment Ivan Malov
2025-12-29 21:35 ` [PATCH 9/9] net/sfc: fix reporting status of autonegotiation to the user Ivan Malov
2025-12-31 19:13 ` [PATCH 0/9] net/sfc: SFN7xxx deprecation and Medford fixes Stephen Hemminger
2026-01-13 15:21 ` Stephen Hemminger
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=ebd63f2d-0a71-7774-d0c1-d2ee3405c4fd@arknetworks.am \
--to=ivan.malov@arknetworks.am \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=viacheslav.galaktionov@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