From: crow@old-fsckful.ath.cx (Andreas Happe)
To: Michal Ludvig <michal@logix.cz>
Cc: Andreas Happe <andreashappe@flatline.ath.cx>,
cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org,
James Morris <jmorris@redhat.com>
Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs
Date: Tue, 7 Sep 2004 16:57:55 +0000 [thread overview]
Message-ID: <20040907165755.GA32032@old-fsckful.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.53.0409071659070.19015@maxipes.logix.cz>
On Tue, Sep 07, 2004 at 05:49:14PM +0200, Michal Ludvig wrote:
> On Tue, 7 Sep 2004, Andreas Happe wrote:
>
> > On Mon, Sep 06, 2004 at 08:49:30PM +0200, Michal Ludvig wrote:
> > > On Wed, 1 Sep 2004, Andreas Happe wrote:
> > BTW: the latest incarnation of the patch uses /sys/class/crypto/<cipher-name>.
>
> Where can I get the updated version?
It's on my home computer (and I'm on vacation quite now ;). will do some additional
testing on friday and will post the patch around the weekend.
It uses class_device (see include/linux/device.h) instead of kobjects.
> This is a compile time thing, e.g. something like:
> .cia_min_keysize = 1,
> .cia_max_keysize = 128
> for variable keysizes, and
> .cia_keysizes = { 128, 192, 256, -1 }
> for discrete keysizes.
> typeof(cia_keysizes) would be "int[]".
can do, but see james morris other patch.
> > Isn't this against the "one value per file" - sysfs rule.
>
> I didn't know about such a rule.
yup, is rather strict.
> Attached is my patch introducing preferences for current cryptoapi. How
> can this be done with the kobject model?
will look into it after I'm home from vacation.
--AndreaS
next prev parent reply other threads:[~2004-09-07 17:09 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 ` 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 [this message]
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 ` [PATCH 2.6.9-rc2 2/2] cryptoapi: make /proc/crypto optional Andreas Happe
2004-09-28 14:32 ` 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=20040907165755.GA32032@old-fsckful.ath.cx \
--to=crow@old-fsckful.ath.cx \
--cc=andreashappe@flatline.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®