DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Matan Azrad <matan@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	dev@dpdk.org
Subject: Re: [PATCH v3] ethdev: fast path async flow API
Date: Wed, 07 Feb 2024 14:31:11 +0100	[thread overview]
Message-ID: <1923081.6tgchFWduM@thomas> (raw)
In-Reply-To: <00761c83-1843-420d-aaeb-d9e49329e191@amd.com>

07/02/2024 11:56, Ferruh Yigit:
> As we synced with Dariusz, there is no good place to document
> ethdev-drivers interfaces in the release notes.
> 
> Also this release there were more ethdev-drivers interface changes,
> around get_ptype(), but those also not documented in the release notes,
> so will remove these ones too.
> 
> 
> But for further release notes, @Thomas, @John, what do you think to add
> a new section (or sub-section) for "internal interface" ?? (device
> abstraction - drivers) interface changes?

When a driver interface is changed, the drivers are updated accordingly.
If it's a driver addition, then we need to follow-up with drivers maintainers.
Adding a new section in the release notes for driver interface changes
is possible but means more work. I'm afraid a lot of changes won't be described,
so I'm not sure of the value of such incomplete doc.



      parent reply	other threads:[~2024-02-07 13:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 18:17 [PATCH] " Dariusz Sosnowski
2024-01-31  9:35 ` [PATCH v2] " Dariusz Sosnowski
2024-01-31 13:20   ` Ori Kam
2024-02-05 11:07   ` Thomas Monjalon
2024-02-05 13:14     ` Dariusz Sosnowski
2024-02-05 14:03       ` Thomas Monjalon
2024-02-06 17:50         ` Dariusz Sosnowski
2024-02-06 17:36   ` [PATCH v3] " Dariusz Sosnowski
2024-02-06 22:21     ` Thomas Monjalon
2024-02-07  0:57       ` Ferruh Yigit
2024-02-07  9:27         ` Thomas Monjalon
2024-02-07 10:47           ` Ferruh Yigit
2024-02-07 10:56             ` Ferruh Yigit
2024-02-07 11:54               ` Ferruh Yigit
2024-02-07 12:06                 ` Dariusz Sosnowski
2024-02-07 13:31               ` Thomas Monjalon [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=1923081.6tgchFWduM@thomas \
    --to=thomas@monjalon.net \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=ferruh.yigit@amd.com \
    --cc=john.mcnamara@intel.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --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).