All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [PATCH v3] crypto/aesni_mb: support newer version library only
Date: Tue, 26 Mar 2019 15:35:08 +0000	[thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C604335B50C1@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <6ad6f6ef-c41e-a8b3-4377-38e96829ab18@nxp.com>

Hi Akhil,

I have discussed with Ferruh in relation to the updating release note 
for this change.
However the change seems not apply to any section under the release note. 

The change does not introduce new feature, nor breaks ABI/API - 
it only changes the requirement of the dependent external library version, 
and makefile/meson will pop up error when the library version is too old and 
prevents compiling.

Regards,
Fan


> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Tuesday, March 26, 2019 9:11 AM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v3] crypto/aesni_mb: support newer version
> library only
> >
> I think this deserve to be updated in the release note as well.
> 


  reply	other threads:[~2019-03-26 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 11:47 [PATCH] crypto/aesni_mb: support newer version library only Fan Zhang
2019-03-04 14:47 ` Trahe, Fiona
2019-03-04 14:57 ` [PATCH v2] " Fan Zhang
2019-03-20 17:44   ` De Lara Guarch, Pablo
2019-03-25 13:58   ` [PATCH v3] " Fan Zhang
2019-03-26  9:10     ` Akhil Goyal
2019-03-26 15:35       ` Zhang, Roy Fan [this message]
2019-03-26 15:43         ` Akhil Goyal
2019-03-29 14:38           ` Akhil Goyal

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=9F7182E3F746AB4EA17801C148F3C604335B50C1@IRSMSX101.ger.corp.intel.com \
    --to=roy.fan.zhang@intel.com \
    --cc=akhil.goyal@nxp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.