From: David Marchand <david.marchand@6wind.com>
To: Jan Viktorin <viktorin@rehivetech.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Olivier Matz <olivier.matz@6wind.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes for device objects
Date: Thu, 7 Apr 2016 19:24:09 +0200 [thread overview]
Message-ID: <CALwxeUu2yGwefQSJdEhpXcvmPgGYbM5dDwNOQCBX1yqFHoB7Yg@mail.gmail.com> (raw)
In-Reply-To: <20160407190950.52f58009@pcviktorin.fit.vutbr.cz>
On Thu, Apr 7, 2016 at 7:09 PM, Jan Viktorin <viktorin@rehivetech.com> wrote:
> On Thu, 7 Apr 2016 19:00:43 +0200
> David Marchand <david.marchand@6wind.com> wrote:
>> >> Following discussions with Jan, here is a deprecation notice to prepare for
>> >> hotplug and rte_device changes to come in 16.07.
>> > As a result, the current rte_driver structure will be renamed to
>> > rte_module and probably reworked in some way due to its semantics and
>> > potential name clash with the new rte_driver struct.
>>
>> If we just introduce some macros like RTE_MODULE_INIT() /
>> RTE_MODULE_EXIT(), we don't need a rte_module object at the moment ?
>>
>
> Well, possibly, we don't need it. At least, it might be hidden and not
> being a part of the API/ABI. Do you need an ack for this?
Yes, please, the process requires 3 acks for this kind of changes.
--
David Marchand
next prev parent reply other threads:[~2016-04-07 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:33 David Marchand
2016-04-07 15:46 ` Jan Viktorin
2016-04-07 17:00 ` David Marchand
2016-04-07 17:09 ` Jan Viktorin
2016-04-07 17:24 ` David Marchand [this message]
2016-04-07 17:27 ` Jan Viktorin
2016-04-08 9:35 ` Olivier Matz
2016-04-08 15:50 ` Thomas Monjalon
2016-04-10 10:05 ` 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=CALwxeUu2yGwefQSJdEhpXcvmPgGYbM5dDwNOQCBX1yqFHoB7Yg@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=thomas.monjalon@6wind.com \
--cc=viktorin@rehivetech.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).