Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266538AbUI0Pzq (ORCPT ); Mon, 27 Sep 2004 11:55:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266574AbUI0Pzp (ORCPT ); Mon, 27 Sep 2004 11:55:45 -0400 Received: from mx1.redhat.com ([66.187.233.31]:39575 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S266538AbUI0Pxe (ORCPT ); Mon, 27 Sep 2004 11:53:34 -0400 Date: Mon, 27 Sep 2004 11:53:27 -0400 (EDT) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: Andreas Happe cc: Michal Ludvig , Andreas Happe , , Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs In-Reply-To: <20040927084149.GA3625@final-judgement.ath.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 691 Lines: 22 On Mon, 27 Sep 2004, Andreas Happe wrote: > just wanted to know if there's any feedback regarding this patch. It > still applies to -rc2 without problems. I'd like to replace /proc/crypto with this, but don't know how to do so with the current development model. Do we start issuing warnings (i.e. "this is going to disappear in one year") via printk now when someone accesses /proc/crypto ? - James -- James Morris - 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/