Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268191AbUIGQ5X (ORCPT ); Tue, 7 Sep 2004 12:57:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268146AbUIGQye (ORCPT ); Tue, 7 Sep 2004 12:54:34 -0400 Received: from mail.kroah.org ([69.55.234.183]:31364 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S268130AbUIGQuU (ORCPT ); Tue, 7 Sep 2004 12:50:20 -0400 Date: Tue, 7 Sep 2004 09:45:00 -0700 From: Greg KH To: James Morris Cc: Andreas Happe , linux-kernel@vger.kernel.org, cryptoapi@lists.logix.cz Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs Message-ID: <20040907164500.GA8530@kroah.com> References: <20040906000446.GA16840@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 883 Lines: 23 On Tue, Sep 07, 2004 at 12:37:48PM -0400, James Morris wrote: > On Sun, 5 Sep 2004, Greg KH wrote: > > > Other than that, I like this move, /proc/crypto isn't the best thing to > > have in a proc filesystem :) > > The only issue is what to do about potentially expanding this into an API > (e.g. open() an algorithm and write to it). Does this sort of thing > belong in sysfs? No, not really. That should be in a special fs just for crypto stuff (cryptofs?) sysfs is for displaying and setting single units of kernel information at at time. So for just showing this crypto information, it would be fine to use. thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/