From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Kevin Laatz <kevin.laatz@intel.com>,
David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, techboard@dpdk.org
Cc: Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [PATCH] doc: announce marking device and driver objects as internal
Date: Tue, 12 Jul 2022 14:38:52 +0300 [thread overview]
Message-ID: <22107325-e08f-ac43-b49a-a75aa68c1952@oktetlabs.ru> (raw)
In-Reply-To: <f7a5832a-4432-356a-3911-eaea5b416491@intel.com>
On 7/12/22 11:24, Kevin Laatz wrote:
> On 10/07/2022 07:17, David Marchand wrote:
>> rte_driver and rte_device are unnecessarily exposed in the public
>> API/ABI.
>> Announce that they will be made opaque in the public API and mark
>> associated API as internal.
>> This impacts all bus, as their driver registration mechanism will be
>> made internal.
>>
>> Note: the PCI bus had a similar deprecation notice that we can remove as
>> the new one is more generic.
>>
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>> ---
>> doc/guides/rel_notes/deprecation.rst | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>
> Thanks for working on this cleanup, David!
>
> Acked-by: Kevin Laatz <kevin.laatz@intel.com>
>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2022-07-12 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 6:17 David Marchand
2022-07-10 8:25 ` Andrew Rybchenko
2022-07-11 2:16 ` Xia, Chenbo
2022-07-11 12:36 ` Thomas Monjalon
2022-07-11 15:01 ` Jerin Jacob
2022-07-12 4:25 ` Hemant Agrawal
2022-07-12 8:24 ` Kevin Laatz
2022-07-12 11:38 ` Andrew Rybchenko [this message]
2022-07-15 16:22 ` Thomas Monjalon
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=22107325-e08f-ac43-b49a-a75aa68c1952@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=mdr@ashroe.eu \
--cc=techboard@dpdk.org \
/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).