From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
techboard@dpdk.org, dev@dpdk.org,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] new QoS/TM API and tree
Date: Tue, 28 Mar 2017 14:47:56 +0200 [thread overview]
Message-ID: <2420741.A9AEKRUsrr@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D8912652780068@IRSMSX108.ger.corp.intel.com>
2017-03-28 10:24, Dumitrescu, Cristian:
> Agree. Let's call the repo dpdk-next-tm and let's limit the scope to TM API, according to the mandate approved by the Tech Board.
>
> Thomas, can we please create this tree asap without any further delay? We need to start the driver development and we are currently blocked by the repo not being created yet. Thanks!
The repository is created:
http://dpdk.org/browse/next/dpdk-next-tm/
Private committer accesses are secured with SSH key.
prev parent reply other threads:[~2017-03-28 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:44 Thomas Monjalon
2017-03-28 9:41 ` Dumitrescu, Cristian
2017-03-28 9:56 ` Thomas Monjalon
2017-03-28 10:09 ` Dumitrescu, Cristian
2017-03-28 10:15 ` Thomas Monjalon
2017-03-28 10:20 ` Jerin Jacob
2017-03-28 10:24 ` Dumitrescu, Cristian
2017-03-28 12:47 ` Thomas Monjalon [this message]
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=2420741.A9AEKRUsrr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=techboard@dpdk.org \
/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).