From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] doc: fix release notes for 16.11
Date: Fri, 11 Nov 2016 18:51:06 +0530 [thread overview]
Message-ID: <b702d605-2745-aae6-0465-b975e87d9689@nxp.com> (raw)
In-Reply-To: <1478865882-15315-1-git-send-email-john.mcnamara@intel.com>
On Friday 11 November 2016 05:34 PM, John McNamara wrote:
[...]
> -* **Improved device/driver hierarchy and generalized hotplugging**
> +* **Improved device/driver hierarchy and generalized hotplugging.**
>
> - Device and driver relationship has been restructured by introducing generic
> - classes. This paves way for having PCI, VDEV and other device types as
> - just instantiated objects rather than classes in themselves. Hotplugging too
> - has been generalized into EAL so that ethernet or crypto devices can use the
> + The device and driver relationship has been restructured by introducing generic
> + classes. This paves the way for having PCI, VDEV and other device types as
> + instantiated objects rather than classes in themselves. Hotplugging has also
> + been generalized into EAL so that Ethernet or crypto devices can use the
> common infrastructure.
>
> - * removed ``pmd_type`` as way of segregation of devices
> - * moved ``numa_node`` and ``devargs`` into ``rte_driver`` from
> + * Removed ``pmd_type`` as a way of segregation of devices.
> + * Moved ``numa_node`` and ``devargs`` into ``rte_driver`` from
> ``rte_pci_driver``. These can now be used by any instantiated object of
> ``rte_driver``.
> - * added ``rte_device`` class and all PCI and VDEV devices inherit from it
> - * renamed devinit/devuninit handlers to probe/remove to make it more
> - semantically correct with respect to device<=>driver relationship
> - * moved hotplugging support to EAL. Hereafter, PCI and vdev can use the
> + * Added ``rte_device`` class and all PCI and VDEV devices inherit from it
> + * Renamed devinit/devuninit handlers to probe/remove to make it more
> + semantically correct with respect to the device <=> driver relationship.
> + * Moved hotplugging support to EAL. Hereafter, PCI and vdev can use the
> APIs ``rte_eal_dev_attach`` and ``rte_eal_dev_detach``.
> - * helpers and support macros have been renamed to make them more synonymous
> + * Renamed helpers and support macros to make them more synonymous
> with their device types
> - (e.g. ``PMD_REGISTER_DRIVER`` => ``RTE_PMD_REGISTER_PCI``)
> + (e.g. ``PMD_REGISTER_DRIVER`` => ``RTE_PMD_REGISTER_PCI``).
> * Device naming functions have been generalized from ethdev and cryptodev
> to EAL. ``rte_eal_pci_device_name`` has been introduced for obtaining
> unique device name from PCI Domain-BDF description.
If it is possible to have a Reviewed-by for a particular part of a patch:
Reviewed-by: Shreyansh Jain <shreyansh.jain@nxp.com>
next prev parent reply other threads:[~2016-11-11 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 12:04 John McNamara
2016-11-11 13:21 ` Shreyansh Jain [this message]
2016-11-13 14: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=b702d605-2745-aae6-0465-b975e87d9689@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).