From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, andrew.rybchenko@oktetlabs.ru,
bruce.richardson@intel.com,
Shepard Siegel <shepard.siegel@atomicrules.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: introduce enable_driver_sdk to install driver headers
Date: Fri, 26 Mar 2021 12:02:55 +0000 [thread overview]
Message-ID: <e03db96a-7b66-47f2-c11e-093dee725408@intel.com> (raw)
In-Reply-To: <20210324162441.GA14991@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On 3/24/2021 4:24 PM, Tyler Retzlaff wrote:
> On Wed, Mar 24, 2021 at 12:30:36PM +0100, Thomas Monjalon wrote:
>> 24/03/2021 12:27, Ferruh Yigit:
>>>
>>> But not sure how to manage the same problem for whole project, if install all
>>> headers in one patch, or add them gradually via separate patches by time ...
>>
>> We did a cleanup in ethdev but not in other driver classes.
>> When the cleanup will be done gradually, the headers
>> must move in this new category driver_sdk_headers.
>
> yes, some headers are not installed now. so they need only to have
> their api marked __rte_internal and installed (since there should be no
> external consumer as a function of not being installed)
>
> the more difficult case is where headers were installed but the api were
> not marked __rte_internal and appear in the stable version.map. for
> those i guess deprecation notice has to be issued before marking as
> internal.
>
Are you referring to any specific APIs, can you share list of them?
next prev parent reply other threads:[~2021-03-26 12:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 19:27 [dpdk-dev] [PATCH] " Tyler Retzlaff
2021-03-12 15:19 ` Ferruh Yigit
2021-03-12 15:25 ` David Marchand
2021-03-12 15:34 ` Bruce Richardson
2021-03-12 15:52 ` Thomas Monjalon
2021-03-12 18:43 ` Tyler Retzlaff
2021-03-12 22:20 ` [dpdk-dev] [PATCH v2] " Tyler Retzlaff
2021-03-15 10:06 ` Bruce Richardson
2021-03-23 17:04 ` Ferruh Yigit
2021-03-24 4:32 ` Tyler Retzlaff
2021-03-24 11:27 ` Ferruh Yigit
2021-03-24 11:30 ` Thomas Monjalon
2021-03-24 16:24 ` Tyler Retzlaff
2021-03-26 12:02 ` Ferruh Yigit [this message]
2021-03-26 20:52 ` Tyler Retzlaff
2021-03-29 9:43 ` Ferruh Yigit
2021-03-29 12:10 ` Thomas Monjalon
2021-03-29 15:23 ` Ferruh Yigit
2021-03-29 19:31 ` Thomas Monjalon
2021-03-30 12:50 ` Ferruh Yigit
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=e03db96a-7b66-47f2-c11e-093dee725408@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=shepard.siegel@atomicrules.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).