From: Evgeniy Polyakov <zbr@ioremap.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
kay.sievers@vrfy.org, linux-kernel@vger.kernel.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Runaway loop with the current git.
Date: Sun, 7 Dec 2008 19:33:24 +0300 [thread overview]
Message-ID: <20081207163323.GB31838@ioremap.net> (raw)
In-Reply-To: <20081207155507.GA15355@gondor.apana.org.au>
On Sun, Dec 07, 2008 at 11:55:07PM +0800, Herbert Xu (herbert@gondor.apana.org.au) wrote:
> Having said that I think this patch should remove this particular
> trigger. Unfortunately I couldn't find a more succinct way of
> expressing this relationship: if ALGAPI is built-in because it's
> selected by an algorithm, and CRYPTO_MANAGER is enabled then we
> require CRYPTO_MANAGER to be built-in as well.
>
> Evgeniy, please let me know whether this fixes the problem.
Holy shit... This looks 'excellent' :)
I will try it tomorrow and report back the results.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-12-07 16:33 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 18:03 Runaway loop with the current git Evgeniy Polyakov
2008-12-05 18:16 ` Alan Cox
2008-12-05 18:32 ` Kay Sievers
2008-12-05 19:27 ` Evgeniy Polyakov
2008-12-05 19:34 ` Alan Cox
2008-12-05 21:12 ` Evgeniy Polyakov
2008-12-05 21:17 ` Kay Sievers
2008-12-05 21:24 ` Evgeniy Polyakov
2008-12-06 2:10 ` Kay Sievers
2008-12-06 16:09 ` Evgeniy Polyakov
2008-12-06 16:16 ` Kay Sievers
2008-12-06 16:56 ` Evgeniy Polyakov
2008-12-06 18:11 ` Kay Sievers
2008-12-06 19:32 ` Kay Sievers
2008-12-06 20:26 ` Evgeniy Polyakov
2008-12-07 3:56 ` Kay Sievers
2008-12-07 4:31 ` Evgeniy Polyakov
2008-12-07 11:23 ` Alan Cox
2008-12-07 11:45 ` Evgeniy Polyakov
2008-12-07 11:58 ` Alan Cox
2008-12-07 13:10 ` Evgeniy Polyakov
2008-12-07 14:02 ` Kay Sievers
2008-12-07 15:08 ` Alan Cox
2008-12-07 14:49 ` Herbert Xu
2008-12-07 15:14 ` Alan Cox
2008-12-07 15:55 ` Herbert Xu
2008-12-07 16:03 ` Kay Sievers
2008-12-07 16:09 ` Alan Cox
2008-12-07 16:21 ` Kay Sievers
2008-12-07 16:57 ` Alan Cox
2008-12-07 17:03 ` Evgeniy Polyakov
2008-12-07 17:24 ` Alan Cox
2008-12-07 17:29 ` Evgeniy Polyakov
2008-12-07 16:31 ` Evgeniy Polyakov
2008-12-07 17:01 ` Alan Cox
2008-12-07 17:13 ` Evgeniy Polyakov
2008-12-07 17:17 ` Kay Sievers
2008-12-07 17:22 ` Kay Sievers
2008-12-07 17:28 ` Alan Cox
2008-12-07 17:39 ` Kay Sievers
2008-12-07 17:51 ` Alan Cox
2008-12-07 18:22 ` Kay Sievers
2008-12-08 3:23 ` Valdis.Kletnieks
2008-12-08 3:56 ` Kay Sievers
2008-12-07 17:44 ` Evgeniy Polyakov
2008-12-07 17:52 ` Alan Cox
2008-12-07 17:54 ` Evgeniy Polyakov
2008-12-07 18:03 ` Alan Cox
2008-12-07 18:13 ` Kay Sievers
2008-12-07 18:15 ` Alan Cox
2008-12-07 18:21 ` Kay Sievers
2008-12-07 18:31 ` Alan Cox
2008-12-07 19:02 ` Kay Sievers
2008-12-07 20:00 ` Alan Cox
2008-12-07 22:26 ` Kay Sievers
2008-12-08 1:18 ` Theodore Tso
2008-12-08 3:35 ` Kay Sievers
2008-12-08 3:35 ` Kay Sievers
2008-12-09 1:09 ` Theodore Tso
2008-12-09 2:00 ` Kay Sievers
2008-12-09 2:00 ` Kay Sievers
2008-12-09 10:13 ` Alan Cox
2008-12-07 16:33 ` Evgeniy Polyakov [this message]
2008-12-08 13:06 ` Evgeniy Polyakov
2008-12-09 0:42 ` Herbert Xu
2008-12-08 13:22 ` Evgeniy Polyakov
2008-12-06 0:29 ` Alan Cox
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=20081207163323.GB31838@ioremap.net \
--to=zbr@ioremap.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=herbert@gondor.apana.org.au \
--cc=kay.sievers@vrfy.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 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.