Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: openwrt@bitsofnetworks.org, lede-dev@lists.infradead.org,
	wireguard@lists.zx2c4.com
Subject: [WireGuard] [PATCH] kernel: expose configuration for padata
Date: Thu, 10 Nov 2016 04:07:44 +0100	[thread overview]
Message-ID: <20161110030744.6402-1-Jason@zx2c4.com> (raw)

The padata API is a powerful framework for doing parallel jobs inside
the kernel, on which various modules in the package feed can depend,
such as WireGuard. There is no item text, so that it does not show up
in menuconfig, as this is only supposed to be an option selected as a
dependency. There as already precedent for this behavior, with
CONFIG_KERNEL_RELAY, on which several packages depend.

Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
 config/Config-kernel.in | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/config/Config-kernel.in b/config/Config-kernel.in
index d8ca76c..9aca2a0 100644
--- a/config/Config-kernel.in
+++ b/config/Config-kernel.in
@@ -224,6 +224,9 @@ config KERNEL_PROC_PAGE_MONITOR
 config KERNEL_RELAY
 	bool
 
+config KERNEL_CRYPTO_PCRYPT
+	bool
+
 config KERNEL_KEXEC
 	bool "Enable kexec support"
 
-- 
2.10.2

             reply	other threads:[~2016-11-10  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  3:07 Jason A. Donenfeld [this message]
2016-11-10  3:08 ` [WireGuard] [PATCH] wireguard: select parallel encryption engine Jason A. Donenfeld
2016-11-10 12:15   ` Baptiste Jonglez
2016-11-14  8:28 ` [WireGuard] [LEDE-DEV] [PATCH] kernel: expose configuration for padata Felix Fietkau
2016-11-14 13:16   ` [WireGuard] [PATCH] kernel: enable pcrypt Jason A. Donenfeld
2016-11-16 19:35     ` Jason A. Donenfeld
2016-11-16 19:35       ` Felix Fietkau
2016-11-16 19:36         ` Jason A. Donenfeld

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=20161110030744.6402-1-Jason@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=lede-dev@lists.infradead.org \
    --cc=openwrt@bitsofnetworks.org \
    --cc=wireguard@lists.zx2c4.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 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).