From: Stephen Hemminger <stephen@networkplumber.org>
To: fengchengwen <fengchengwen@huawei.com>
Cc: Thierry Herbelot <thierry.herbelot@6wind.com>, <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>, <stable@dpdk.org>
Subject: Re: [PATCH] ethdev: fix get_reg_info
Date: Mon, 10 Mar 2025 08:34:33 -0700 [thread overview]
Message-ID: <20250310083433.39baff9c@hermes.local> (raw)
In-Reply-To: <11224e6b-4101-415e-bab3-b526688bace2@huawei.com>
On Fri, 7 Mar 2025 17:40:17 +0800
fengchengwen <fengchengwen@huawei.com> wrote:
> I think there are ambiguities in the original API definition:
> 1) the width was used as an output parameter in current all PMD impl.
> 2) the offset was unused in current all PMD impl.
>
> But maybe other non-opensource PMD will use these two field.
> So I think it's OK to copy the two fields (maybe another field "version") before invoke _ext API.
It is not necessary to accommodate drivers not in the current tree. If they get broken, not our problem.
Having a stable driver API was never agreed to.
prev parent reply other threads:[~2025-03-10 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 11:58 Thierry Herbelot
2025-02-19 18:45 ` Stephen Hemminger
2025-03-06 16:36 ` Thomas Monjalon
2025-03-07 9:33 ` fengchengwen
2025-03-07 9:40 ` fengchengwen
2025-03-10 15:34 ` Stephen Hemminger [this message]
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=20250310083433.39baff9c@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.com \
--cc=thomas@monjalon.net \
/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).