From: Thomas Monjalon <thomas@monjalon.net>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>, ferruh.yigit@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: fill git trees for net and crypto API
Date: Sun, 12 Nov 2017 05:51:28 +0100 [thread overview]
Message-ID: <1746970.1JDTCvcneo@xps> (raw)
In-Reply-To: <20171106163822.2849-1-pablo.de.lara.guarch@intel.com>
> > The ethdev API (including rte_flow) is managed in the dpdk-next-net tree.
> > The crypto and security API is managed in the dpdk-next-crypto tree.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> >
> > Pablo, do you agree to manage rte_security patches in the crypto tree?
>
> Hi Thomas,
>
> I think it will depend on the amount of work that will be done in the
> network drivers in the future. Can anyone working on the security
> library say how much work is expected to be done there?
>
> If there is not going to be huge work there, I don't mind
> taking this in the subtree.
Applied without the rte_security one, as it is still a grey area.
prev parent reply other threads:[~2017-11-12 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 11:36 Thomas Monjalon
2017-11-06 16:38 ` Pablo de Lara
2017-11-12 4:51 ` 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=1746970.1JDTCvcneo@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=pablo.de.lara.guarch@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 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).