From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] Change rte_eal_vdev_init to update port_id
Date: Sun, 09 Aug 2015 11:21:04 +0200 [thread overview]
Message-ID: <2618969.8Z8RK36gE9@xps13> (raw)
In-Reply-To: <CAFb4SLDLin+h8u8d5VNHPgxv_vQQn_3sHk1+2HKkHcQeeG-njw@mail.gmail.com>
2015-08-07 15:06, Ravi Kerur:
> On Thu, Aug 6, 2015 at 7:25 PM, Tetsuya Mukawa <mukawa@igel.co.jp> wrote:
> > On 2015/08/07 3:04, Ravi Kerur wrote:
> > Hi Thomas,
> >
> > Could you please make sure API consistency?
> > Is it ok to add above functions to DPDK_2.1 even though we are in RC
> > phase, or need to add to DPDK_2.2?
> >
> Same question. If it's targeted for 2.2 then I will modify this.
Why should it be in 2.1?
Is there something I missed which makes it an important fix?
If no, please stop sending this kind of patch until the end of the 2.1 release.
Thanks
next prev parent reply other threads:[~2015-08-09 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 18:04 Ravi Kerur
2015-08-07 2:25 ` Tetsuya Mukawa
2015-08-07 22:06 ` Ravi Kerur
2015-08-09 9:21 ` Thomas Monjalon [this message]
2015-08-10 5:31 ` Tetsuya Mukawa
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=2618969.8Z8RK36gE9@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.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).