From: Antoine Tenart <antoine.tenart@bootlin.com>
To: Pascal van Leeuwen <pascalvanl@gmail.com>
Cc: linux-crypto@vger.kernel.org, antoine.tenart@bootlin.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
Pascal van Leeuwen <pvanleeuwen@verimatrix.com>
Subject: Re: [PATCH] crypto: inside-secure - remove unused struct entry
Date: Fri, 5 Jul 2019 16:18:00 +0200 [thread overview]
Message-ID: <20190705141800.GE3926@kwain> (raw)
In-Reply-To: <1562314645-22949-1-git-send-email-pvanleeuwen@verimatrix.com>
Hello Pascal,
On Fri, Jul 05, 2019 at 10:17:25AM +0200, Pascal van Leeuwen wrote:
> This patch removes 'engines' from struct safexcel_alg_template, as it is
> no longer used.
>
> Signed-off-by: Pascal van Leeuwen <pvanleeuwen@verimatrix.com>
> ---
> drivers/crypto/inside-secure/safexcel.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/crypto/inside-secure/safexcel.h b/drivers/crypto/inside-secure/safexcel.h
> index 379d0b0..30a222e 100644
> --- a/drivers/crypto/inside-secure/safexcel.h
> +++ b/drivers/crypto/inside-secure/safexcel.h
> @@ -660,7 +660,6 @@ struct safexcel_ahash_export_state {
> struct safexcel_alg_template {
> struct safexcel_crypto_priv *priv;
> enum safexcel_alg_type type;
> - u32 engines;
This patch can't be applied to the cryptodev branch, as 'engines' is
still used. I guess this is done as other (non-applied) patches are
removing the use of this member.
You should wait for either those patches to be merged (or directly
integrate this change in a newer version of those patches), or send this
patch in the same series. Otherwise it's problematic as you do not know
which patches will be applied first.
Thanks,
Antoine
--
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-05 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 8:17 [PATCH] crypto: inside-secure - remove unused struct entry Pascal van Leeuwen
2019-07-05 14:18 ` Antoine Tenart [this message]
2019-07-05 14:32 ` Pascal Van Leeuwen
2019-07-05 14:39 ` Antoine Tenart
2019-07-05 14:54 ` Pascal Van Leeuwen
2019-07-05 15:57 ` Antoine Tenart
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=20190705141800.GE3926@kwain \
--to=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pascalvanl@gmail.com \
--cc=pvanleeuwen@verimatrix.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.