From: Andreas Happe <andreashappe@flatline.ath.cx>
To: James Morris <jmorris@redhat.com>
Cc: Michal Ludvig <michal@logix.cz>,
Andreas Happe <crow@old-fsckful.ath.cx>,
cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.9-rc2 2/2] cryptoapi: make /proc/crypto optional
Date: Tue, 28 Sep 2004 14:23:32 +0200 [thread overview]
Message-ID: <20040928122332.GB21010@final-judgement.ath.cx> (raw)
In-Reply-To: <20040928122117.GA21010@final-judgement.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
creates a new Kconfig entry for the /proc/crypto - file and mark it as
OBSOLETE. This patch is just compile tested and applies after
patch-2.6.9-rc1-cryptoapi-class-2.
Signed-of-by: Andreas Happe <andreashappe@snikt.net>
[-- Attachment #2: patch-2.6.9-rc2-make_proc_crypto_optional-1 --]
[-- Type: text/plain, Size: 1077 bytes --]
diff -u -r -N linux-2.6.8/crypto/Kconfig linux-sysfs/crypto/Kconfig
--- linux-2.6.8/crypto/Kconfig 2004-09-28 12:50:31.000000000 +0200
+++ linux-sysfs/crypto/Kconfig 2004-09-28 12:18:25.000000000 +0200
@@ -16,6 +16,15 @@
HMAC: Keyed-Hashing for Message Authentication (RFC2104).
This is required for IPSec.
+config CRYPTO_PROC
+ bool "Legacy /proc/crypto interface (OBSOLETE)"
+ depends on PROC_FS && CRYPTO
+ help
+ Displays cipher specific information via /proc/crypto.
+ Please use /sysfs/class/crypto instead.
+
+ When in double say Y.
+
config CRYPTO_NULL
tristate "Null algorithms"
depends on CRYPTO
diff -u -r -N linux-2.6.8/crypto/Makefile linux-sysfs/crypto/Makefile
--- linux-2.6.8/crypto/Makefile 2004-09-28 12:52:40.000000000 +0200
+++ linux-sysfs/crypto/Makefile 2004-09-28 12:14:14.000000000 +0200
@@ -2,7 +2,7 @@
# Cryptographic API
#
-proc-crypto-$(CONFIG_PROC_FS) = proc.o
+proc-crypto-$(CONFIG_CRYPTO_PROC) = proc.o
sysfs-crypto-$(CONFIG_SYSFS) = sysfs.o
obj-$(CONFIG_CRYPTO) += api.o scatterwalk.o cipher.o digest.o compress.o \
next prev parent reply other threads:[~2004-09-28 12:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040831175449.GA2946@final-judgement.ath.cx>
[not found] ` <Xine.LNX.4.44.0409010043020.30561-100000@thoron.boston.redhat.com>
2004-09-01 8:28 ` [cryptoapi/sysfs] display cipher details in sysfs Andreas Happe
2004-09-06 0:04 ` Greg KH
2004-09-07 16:37 ` James Morris
2004-09-07 16:45 ` Greg KH
2004-09-07 16:47 ` Michal Ludvig
2004-09-07 16:52 ` Greg KH
2004-09-06 18:49 ` Michal Ludvig
2004-09-07 14:35 ` Andreas Happe
2004-09-07 15:49 ` Michal Ludvig
2004-09-07 16:57 ` Andreas Happe
2004-09-10 11:21 ` Andreas Happe
2004-09-10 10:55 ` Andreas Happe
2004-09-27 8:41 ` Andreas Happe
2004-09-27 9:10 ` Michal Ludvig
2004-09-28 12:34 ` Andreas Happe
2004-09-29 9:36 ` Andreas Happe
2004-09-29 9:37 ` Andreas Happe
2004-09-29 14:13 ` Michal Ludvig
2004-09-29 13:13 ` Michal Ludvig
2004-09-27 15:53 ` James Morris
2004-09-28 12:21 ` [PATCH 2.6.9-rc2 1/2] cryptoapi: update sysfs-patch Andreas Happe
2004-09-28 12:23 ` Andreas Happe [this message]
2004-09-28 14:32 ` [PATCH 2.6.9-rc2 2/2] cryptoapi: make /proc/crypto optional Sven Schuster
2004-09-29 8:40 ` Andreas Happe
2004-09-07 16:36 ` [cryptoapi/sysfs] display cipher details in sysfs James Morris
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=20040928122332.GB21010@final-judgement.ath.cx \
--to=andreashappe@flatline.ath.cx \
--cc=crow@old-fsckful.ath.cx \
--cc=cryptoapi@lists.logix.cz \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@logix.cz \
/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
all inboxes | Powered by JetHome®