From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH] crypto: fix compile errors of XTS
Date: Wed, 17 Feb 2016 07:55:21 +0000 [thread overview]
Message-ID: <20160217075521.GC16041@gondor.apana.org.au> (raw)
In-Reply-To: <17540790.vcykgraQyO@positron.chronox.de>
On Wed, Feb 17, 2016 at 07:00:01AM +0100, Stephan Mueller wrote:
> Commit 28856a9e52c7 missed the addition of the crypto/xts.h include file
> for different architecture-specific AES implementations.
>
> Signed-off-by: Stephan Mueller <smueller@chronox.de>
Applied.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2016-02-17 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 6:00 [PATCH] crypto: fix compile errors of XTS Stephan Mueller
2016-02-17 7:55 ` Herbert Xu [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=20160217075521.GC16041@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=fengguang.wu@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=smueller@chronox.de \
/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