From: "Yang, Ziye" <ziye.yang@intel.com>
To: Panu Matilainen <pmatilai@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] PCI: ABI change request for adding new field in rte_pci_id structure
Date: Tue, 16 Feb 2016 07:43:35 +0000 [thread overview]
Message-ID: <FA6C2217B01E9D48A581BB4866021014017041B8@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <56C2D209.8000303@redhat.com>
Hi Panu,
" ABI breakage announcements go into doc/guides/rel_notes/deprecation.rst,
see the examples there. Also you can't break the ABI in the version under development but only the next one, so right now the earliest ABI breakage opportunity is in the release *after* 16.04, which is supposed to be 16.07 according to the roadmap."
So I only need to do the ABI breakage announcements into doc/guides/rel_notes/deprecation.rst, right?
Thanks.
Best Regards,
Ziye Yang
-----Original Message-----
From: Panu Matilainen [mailto:pmatilai@redhat.com]
Sent: Tuesday, February 16, 2016 3:39 PM
To: Yang, Ziye <ziye.yang@intel.com>; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] PCI: ABI change request for adding new field in rte_pci_id structure
On 02/16/2016 05:16 AM, Ziye Yang wrote:
> From: Ziye <ziye.yang@intel.com>
>
> The purpose of this patch is used to add a new field "class" in
> rte_pci_id structure. The new class field includes class_id,
> subcalss_id, programming interface of a pci device.
> With this field, we can identify pci device by its class info, which
> can be more flexible instead of probing the device by vendor_id OR
> device_id OR subvendor_id OR subdevice_id.
> For example, we can probe all nvme devices by class field, which can
> be quite convenient.
>
> Signed-off-by: Ziye Yang <ziye.yang@intel.com>
> ---
> doc/guides/rel_notes/release_16_04.rst | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/doc/guides/rel_notes/release_16_04.rst
> b/doc/guides/rel_notes/release_16_04.rst
> index 27fc624..fe843a5 100644
> --- a/doc/guides/rel_notes/release_16_04.rst
> +++ b/doc/guides/rel_notes/release_16_04.rst
> @@ -95,9 +95,10 @@ This section should contain API changes. Sample format:
> ABI Changes
> -----------
>
> -* Add a short 1-2 sentence description of the ABI change that was
> announced in
> - the previous releases and made in this release. Use fixed width
> quotes for
> - ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
> +* New field ``class`` is added into ``rte_pci_id`` structure. This
> +new
> + added ``class`` field can be used to probe pci devices by class
> +related
> + info. With this new field, the size of structure ``rte_pci_device``
> +will
> + be increased.
>
>
> Shared Library Versions
>
ABI breakage announcements go into doc/guides/rel_notes/deprecation.rst,
see the examples there. Also you can't break the ABI in the version under development but only the next one, so right now the earliest ABI breakage opportunity is in the release *after* 16.04, which is supposed to be 16.07 according to the roadmap.
- Panu -
next prev parent reply other threads:[~2016-02-16 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 3:16 Ziye Yang
2016-02-16 7:38 ` Panu Matilainen
2016-02-16 7:43 ` Yang, Ziye [this message]
2016-02-16 7:55 ` Panu Matilainen
[not found] <1453689419-237252>
2016-02-16 4:08 ` Ziye Yang
-- strict thread matches above, loose matches on Subject: below --
2016-01-25 2:36 [dpdk-dev] [PATCH] " Ziye Yang
2016-02-16 4:15 ` [dpdk-dev] [PATCH v2] " Ziye Yang
2016-02-16 10:11 ` Bruce Richardson
2016-02-16 10:34 ` 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=FA6C2217B01E9D48A581BB4866021014017041B8@shsmsx102.ccr.corp.intel.com \
--to=ziye.yang@intel.com \
--cc=dev@dpdk.org \
--cc=pmatilai@redhat.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).