From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Akhil Goyal <akhil.goyal@nxp.com>,
"nicolas.chautru@intel.com" <nicolas.chautru@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"trix@redhat.com" <trix@redhat.com>,
bluca@debian.org, ktraynor@redhat.com
Subject: Re: [dpdk-dev] [PATCH 0/2] baseband: fix drivers API
Date: Wed, 7 Oct 2020 12:12:00 +0200
Message-ID: <3b075a8e-cf25-0dad-b638-88347adc6268@redhat.com> (raw)
In-Reply-To: <2443257.4GMkhuKzMg@thomas>
On 10/7/20 12:09 PM, Thomas Monjalon wrote:
> 07/10/2020 10:22, Maxime Coquelin:
>> Hi Akhil,
>>
>> Adding Thomas as he pulls your tree.
>>
>> On 10/6/20 9:42 PM, Akhil Goyal wrote:
>>>
>>>>
>>>> The series prefixes drivers APIs with rte_<drv_name>_ in
>>>> order to avoid namespace pollution.
>>>>
>>>> These APIs are experimental, so no need to follow the
>>>> deprecation process.
>>>>
>>> Added Fixes commit in patch description.
>>
>> Thanks for applying it to your tree.
>>
>> I did not add Fixes tag and Cc'ed stable@dpdk.org on purpose,
>> because I thought it is was not a good idea to backport API changes,
>> even if this is experimental it might be annoying for the user.
>>
>> Thomas, do you confirm?
>
> Absolutely: API must not change in a stable branch.
>
> If an API is changed, it must be in the release notes.
Ok, even for experimental APIs? I thought not.
> But stable branches are not allowed to update such sections
> of the release notes.
>
>
next prev parent reply other threads:[~2020-10-07 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 8:59 Maxime Coquelin
2020-10-02 8:59 ` [dpdk-dev] [PATCH 1/2] baseband/fpga_5gnr_fec: fix API naming Maxime Coquelin
2020-10-03 15:26 ` Tom Rix
2020-10-05 7:11 ` Maxime Coquelin
2020-10-05 7:28 ` Maxime Coquelin
2020-10-02 8:59 ` [dpdk-dev] [PATCH 2/2] baseband/fpga_lte_fec: " Maxime Coquelin
2020-10-03 15:31 ` Tom Rix
2020-10-06 19:42 ` [dpdk-dev] [PATCH 0/2] baseband: fix drivers API Akhil Goyal
2020-10-07 8:22 ` Maxime Coquelin
2020-10-07 10:09 ` Thomas Monjalon
2020-10-07 10:12 ` Maxime Coquelin [this message]
2020-10-07 10:29 ` Thomas Monjalon
2020-10-07 10:52 ` Maxime Coquelin
2020-10-07 11:06 ` Thomas Monjalon
2020-10-07 11:07 ` Thomas Monjalon
2020-10-07 12:05 ` Akhil Goyal
2020-10-07 12:19 ` Maxime Coquelin
2020-10-07 11:09 ` Maxime Coquelin
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=3b075a8e-cf25-0dad-b638-88347adc6268@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
--cc=trix@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
DPDK patches and discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
dev@dpdk.org
public-inbox-index dev
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://inbox.dpdk.org/inbox.dpdk.dev
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git