From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: CTR mode: Kconfig cyclic dependency
Date: Sun, 12 Jun 2016 13:05:14 +0200 [thread overview]
Message-ID: <2056366.RZreOqocPk@positron.chronox.de> (raw)
In-Reply-To: <20160612105828.GB807@gondor.apana.org.au>
Am Sonntag, 12. Juni 2016, 18:58:28 schrieb Herbert Xu:
Hi Herbert,
> On Thu, Jun 09, 2016 at 11:07:06AM +0200, Stephan Mueller wrote:
> > during the finalization of my patch set for converting the CTR DRBG over
> > to
> > CTR AES, I ran into a Kconfig problem. Maybe you have an idea how to
> > resolve it.
>
> Once I finish the skcipher conversion CTR will no longer need SEQIV.
> If it's stopping your work right now I think you can just kill the
> SEQIV selection by CTR right now since the only user IPsec doesn't
> select CTR anyway.
For now, I use depends on just to ensure a basic consistency. I think I can
wait for your skcipher conversion.
Thanks.
Ciao
Stephan
prev parent reply other threads:[~2016-06-12 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 9:07 CTR mode: Kconfig cyclic dependency Stephan Mueller
2016-06-12 10:58 ` Herbert Xu
2016-06-12 11:05 ` Stephan Mueller [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=2056366.RZreOqocPk@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/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