From: Panu Matilainen <pmatilai@redhat.com>
To: "Yang, Ziye" <ziye.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2] PCI: ABI change request for adding new field in rte_pci_id structure
Date: Tue, 16 Feb 2016 09:55:26 +0200 [thread overview]
Message-ID: <56C2D5EE.8070004@redhat.com> (raw)
In-Reply-To: <FA6C2217B01E9D48A581BB4866021014017041B8@shsmsx102.ccr.corp.intel.com>
On 02/16/2016 09:43 AM, Yang, Ziye wrote:
> 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?
>
Yes.
The version-specific release notes ABI/API changes section is to be
updated along with the actual changes to the code.
If you haven't already done so, do read
http://dpdk.org/doc/guides/contributing/versioning.html
- Panu -
next prev parent reply other threads:[~2016-02-16 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 3:16 [PATCH v2] PCI: ABI change request for adding new field in rte_pci_id structure Ziye Yang
2016-02-16 7:38 ` Panu Matilainen
2016-02-16 7:43 ` Yang, Ziye
2016-02-16 7:55 ` Panu Matilainen [this message]
[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 [PATCH] " Ziye Yang
2016-02-16 4:15 ` [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=56C2D5EE.8070004@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.org \
--cc=ziye.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.