DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] dpdk-next-crypto not up to date
Date: Thu, 13 Aug 2020 08:35:58 +0000	[thread overview]
Message-ID: <VI1PR04MB31685200B5C404446B5E5B6FE6430@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <BY5PR11MB391009A34D3473B8FF1706EEED430@BY5PR11MB3910.namprd11.prod.outlook.com>

Hi Adam,

It is updated now. But I don't see that you are blocked in any way due to this. You can send the patches over master if the crypto tree is behind master. It will be updated to the latest master whenever it is synced. So there will be no conflict.

Regards,
Akhil


Hi.

Please merge main dpdk branch into dpdk-next-crypto.
20.08 was released few days ago but I don't see any new commits here: https://git.dpdk.org/next/dpdk-next-crypto/<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fnext%2Fdpdk-next-crypto%2F&data=02%7C01%7Cakhil.goyal%40nxp.com%7Cf7703b5c417b4f936bda08d83f603f34%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637329029897234535&sdata=gI0mg2c8CTfouQWlZG1AceB42q%2BXy320GTC7JCczBis%3D&reserved=0>
I can't prepare and send to ML any patches because of the lack of new release notes for 20.11 and few other recently updated files.



  reply	other threads:[~2020-08-13  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  8:09 Dybkowski, AdamX
2020-08-13  8:35 ` Akhil Goyal [this message]
2020-08-13  8:43   ` Dybkowski, AdamX

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=VI1PR04MB31685200B5C404446B5E5B6FE6430@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=adamx.dybkowski@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).