From: Thomas Monjalon <thomas@monjalon.net>
To: santosh <santosh.shukla@caviumnetworks.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
dev@dpdk.org, jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH] mempool: add notice to change mempool API/ABI
Date: Thu, 20 Jul 2017 14:26:35 +0300 [thread overview]
Message-ID: <4920445.JIvm8nXJvS@xps> (raw)
In-Reply-To: <e819f861-f933-1f6f-a35a-0e2321374f42@caviumnetworks.com>
20/07/2017 12:27, santosh:
> On Thursday 20 July 2017 02:16 PM, Olivier Matz wrote:
>
> > On Thu, 13 Jul 2017 09:12:31 +0000, Santosh Shukla <santosh.shukla@caviumnetworks.com> wrote:
> >> [PATCH] mempool: add notice to change mempool API/ABI
> > I think the usual titles for these notices are more:
> >
> > doc: announce API/ABI changes for mempool
>
> in v2.
>
> > Ideally, the title should describe more precisely the kind of
> > changes. In that particular case, it looks quite difficult,
> > so just saying "mempool" looks okay. Maybe Thomas will prefer
> > one entry per change, I don't know.
> >
> Thomas, Are you fine with approach?
Yes it is OK.
The important words are "announce", "API" and "mempool".
As you are breaking the API, no need to be explicit about ABI.
next prev parent reply other threads:[~2017-07-20 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 9:12 Santosh Shukla
2017-07-20 8:46 ` Olivier Matz
2017-07-20 9:27 ` santosh
2017-07-20 11:26 ` Thomas Monjalon [this message]
2017-07-20 10:29 ` [dpdk-dev] [PATCH v2] doc: announce API/ABI changes for mempool Santosh Shukla
2017-07-21 6:26 ` santosh
2017-08-03 14:21 ` Jerin Jacob
2017-08-03 14:30 ` santosh
2017-08-05 20:24 ` Olivier MATZ
2017-08-08 0:10 ` 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=4920445.JIvm8nXJvS@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olivier.matz@6wind.com \
--cc=santosh.shukla@caviumnetworks.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).