From: Thomas Monjalon <thomas@monjalon.net>
To: Arnon Warshavsky <arnon@qwilt.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Bruce Richardson <bruce.richardson@intel.com>,
ranjit.menon@intel.com, anand.rawat@intel.com,
Pallavi Kadam <pallavi.kadam@intel.com>,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
"O'Hare, Cathal" <cathal.ohare@intel.com>,
Arnon Warshavsky <arnonw@qwilt.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce ABI change on eal and kni
Date: Wed, 08 May 2019 13:07:39 +0200 [thread overview]
Message-ID: <5113628.MvIexMTWk3@xps> (raw)
In-Reply-To: <CAKy9EB0DSyvOR6zmqr9WH=UwQWJkv9+SCBCKTWK36r8JigskZw@mail.gmail.com>
07/05/2019 11:57, Arnon Warshavsky:
> >
> >
> > Changing 'kni_fifo_init()' return type shouldn't be a problem at all,
> > perhaps it would be a problem if the content of the fifo changed but it is
> > not
> > the case.
> >
>
> Should I move this patch to deferred or reject?
It can be set to "rejected".
I am preparing a deprecation notice for rte_eal_remote_launch
and rte_metrics_init.
next prev parent reply other threads:[~2019-05-08 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 14:58 [dpdk-dev] [PATCH] doc: announce ABI change on eal and kni Arnon Warshavsky
2019-04-28 16:23 ` Stephen Hemminger
2019-04-29 9:28 ` Ferruh Yigit
2019-04-29 16:24 ` Stephen Hemminger
2019-04-29 17:19 ` Ferruh Yigit
2019-05-07 9:57 ` Arnon Warshavsky
2019-05-08 11:07 ` Thomas Monjalon [this message]
2019-05-08 20:22 ` Arnon Warshavsky
2019-05-08 20:25 ` 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=5113628.MvIexMTWk3@xps \
--to=thomas@monjalon.net \
--cc=anand.rawat@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=arnon@qwilt.com \
--cc=arnonw@qwilt.com \
--cc=bruce.richardson@intel.com \
--cc=cathal.ohare@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=stephen@networkplumber.org \
--cc=wenzhuo.lu@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.