From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Store and transmit own neighborhood hash
Date: Tue, 20 Sep 2016 15:01:04 +0200 [thread overview]
Message-ID: <2405543.TZHNHoipHL@bentobox> (raw)
In-Reply-To: <20160920121245.593-2-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
[...]
> diff --git a/net/batman-adv/Kconfig b/net/batman-adv/Kconfig
> index f20742c..35e220e 100644
> --- a/net/batman-adv/Kconfig
> +++ b/net/batman-adv/Kconfig
> @@ -18,6 +18,7 @@ config BATMAN_ADV
> config BATMAN_ADV_BATMAN_V
> bool "B.A.T.M.A.N. V protocol (experimental)"
> depends on BATMAN_ADV && CFG80211=y || (CFG80211=m && BATMAN_ADV=m)
> + depends on CRYPTO_SHA512
> default n
> help
> This option enables the B.A.T.M.A.N. V protocol, the successor
Nearly everyone else seems to select the crypto sha512 module (maybe we should
do the same?):
crypto/Kconfig: select CRYPTO_SHA512
crypto/Kconfig: select CRYPTO_SHA512
crypto/Kconfig: select CRYPTO_SHA512
crypto/Kconfig: select CRYPTO_SHA512
drivers/crypto/Kconfig: select CRYPTO_SHA512
drivers/crypto/chelsio/Kconfig: select CRYPTO_SHA512
drivers/crypto/qat/Kconfig: select CRYPTO_SHA512
drivers/staging/lustre/lustre/Kconfig: select CRYPTO_SHA512
init/Kconfig: select CRYPTO_SHA512
init/Kconfig: select CRYPTO_SHA512
security/integrity/ima/Kconfig: depends on CRYPTO_SHA512 && !IMA_TEMPLATE
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-20 13:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 12:12 [B.A.T.M.A.N.] Broadcast Avoidances, Neighborhood Hash Linus Lüssing
2016-09-20 12:12 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Store and transmit own neighborhood hash Linus Lüssing
2016-09-20 13:01 ` Sven Eckelmann [this message]
2016-09-29 15:31 ` Sven Eckelmann
2016-10-06 1:55 ` Linus Lüssing
2016-10-06 3:03 ` Linus Lüssing
2016-10-06 15:41 ` Linus Lüssing
2016-09-29 16:05 ` Sven Eckelmann
2016-09-29 16:39 ` Sven Eckelmann
2016-09-20 12:12 ` [B.A.T.M.A.N.] [PATCH 2/3] batman-adv: Introduce packet type independent TVLV handler API Linus Lüssing
2016-09-29 16:05 ` Sven Eckelmann
2016-09-29 16:46 ` Sven Eckelmann
2016-09-20 12:12 ` [B.A.T.M.A.N.] [PATCH 3/3] batman-adv: Evaluate and use neighborhood hash TVLV Linus Lüssing
2016-09-29 15:48 ` Sven Eckelmann
2016-09-29 16:05 ` Sven Eckelmann
2016-09-29 16:55 ` Sven Eckelmann
2016-09-20 12:23 ` [B.A.T.M.A.N.] Broadcast Avoidances, Neighborhood Hash Linus Lüssing
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=2405543.TZHNHoipHL@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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;
as well as URLs for NNTP newsgroup(s).