From: "Mokhtar, Amr" <amr.mokhtar@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and security
Date: Fri, 20 Apr 2018 10:48:47 +0000 [thread overview]
Message-ID: <3D3765A8CDB52A4C8B410430AA19CB236ECAF5A3@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CCD8647@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday 19 April 2018 14:14
> To: Mokhtar, Amr <amr.mokhtar@intel.com>; thomas@monjalon.net
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and
> security
>
> Hi Amr,
>
> > -----Original Message-----
> > From: Mokhtar, Amr
> > Sent: Friday, April 13, 2018 8:28 PM
> > To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> > thomas@monjalon.net
> > Cc: dev@dpdk.org
> > Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev
> and
> > security
> >
> > Hi Pablo, Thomas,
> > There are some update patches undergoing submission for bbdev on
> master.
> > Do we need to copy them over from master to next-crypto-subtree?
> > And how this will work in the future? Will all future patches go to next
> subtree
> > and back to master?
>
> Sorry for not replying to this earlier. These patches will get merged in next-
> crypto subtree
> and then, after a pull request, Thomas will merge the changes into mainline.
>
> Pablo
Sounds great. Thanks Pablo.
next prev parent reply other threads:[~2018-04-20 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 8:14 Pablo de Lara
2018-04-13 19:28 ` Mokhtar, Amr
2018-04-19 13:13 ` De Lara Guarch, Pablo
2018-04-20 10:48 ` Mokhtar, Amr [this message]
2018-04-27 22:05 ` 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=3D3765A8CDB52A4C8B410430AA19CB236ECAF5A3@IRSMSX101.ger.corp.intel.com \
--to=amr.mokhtar@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas@monjalon.net \
/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).