Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264919AbTFWI0i (ORCPT ); Mon, 23 Jun 2003 04:26:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264929AbTFWI03 (ORCPT ); Mon, 23 Jun 2003 04:26:29 -0400 Received: from hera.cwi.nl ([192.16.191.8]:19895 "EHLO hera.cwi.nl") by vger.kernel.org with ESMTP id S264919AbTFWI02 (ORCPT ); Mon, 23 Jun 2003 04:26:28 -0400 From: Andries.Brouwer@cwi.nl Date: Mon, 23 Jun 2003 10:40:32 +0200 (MEST) Message-Id: To: Andries.Brouwer@cwi.nl, hch@infradead.org Subject: Re: [PATCH] loop.c - part 1 of many Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 602 Lines: 16 hch: > Once you start touching loop_{,un}register_transfer please also get > rid of the array in favour of a linked list.. Why do you think that might be a good idea? General elegance? The array is legacy only - it will not grow. It has length 20, and only three entries are frequently used: 18 for CryptoAPI, 16 for loopAES, 0 for no encryption. Andries - 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/