DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
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 bus object as internal
Date: Tue, 5 Jul 2022 10:13:39 +0530	[thread overview]
Message-ID: <64bffccf-0d88-740a-4a1a-fd5ca47c01f1@oss.nxp.com> (raw)
In-Reply-To: <8738a46e-6baf-6144-12b3-acf0c811c06a@intel.com>

Acked-by:  Hemant Agrawal <hemant.agrawal@nxp.com>

On 7/4/2022 7:59 PM, Kevin Laatz wrote:
> On 30/06/2022 10:41, David Marchand wrote:
>> rte_bus is unnecessarily exposed in the public API/ABI.
>> Besides, we had cases where extending rte_bus was necessary.
>> Announce that rte_bus will be made opaque in the public API and mark
>> associated API as internal.
>>
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>> ---
>> A RFC series of the intended changes is available at:
>> https://patches.dpdk.org/project/dpdk/list/?series=23811&state=%2A&archive=both 
>>
>>
>> ---
>>   doc/guides/rel_notes/deprecation.rst | 6 ++++++
>>   1 file changed, 6 insertions(+)
>>
> Acked-by: Kevin Laatz <kevin.laatz@intel.com>
>

  reply	other threads:[~2022-07-05  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  9:41 David Marchand
2022-06-30  9:54 ` Bruce Richardson
2022-06-30 14:36   ` Thomas Monjalon
2022-07-04 14:29 ` Kevin Laatz
2022-07-05  4:43   ` Hemant Agrawal [this message]
2022-07-05  6:59     ` Andrew Rybchenko
2022-07-15 16:16 ` 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=64bffccf-0d88-740a-4a1a-fd5ca47c01f1@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --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).