Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261298AbUCVRhB (ORCPT ); Mon, 22 Mar 2004 12:37:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261532AbUCVRhA (ORCPT ); Mon, 22 Mar 2004 12:37:00 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:14812 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S261298AbUCVRg7 (ORCPT ); Mon, 22 Mar 2004 12:36:59 -0500 Message-ID: <405F2429.6040905@pobox.com> Date: Mon, 22 Mar 2004 12:36:41 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Clay Haapala CC: James Morris , Jouni Malinen , "David S. Miller" , linux-kernel@vger.kernel.org, Matt_Domsch@dell.com Subject: Re: [PATCH] lib/libcrc32c implementation References: <405F1B99.3050707@pobox.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 909 Lines: 33 Clay Haapala wrote: > On Mon, 22 Mar 2004, Jeff Garzik spake thusly: > >>Clay Haapala wrote: >> >>>This patch agains 2.6.4 kernel code implements the CRC32C >>>algorithm. The routines are based on the same design as the >>>existing CRC32 code. Licensing is intended to be identical (GPL). >>>The immediate customer of this code is the wrapper code in >>>crypto/crc32c, available in another patch. >> >> >>Why not call it 'crc32c' like its cousin crc32, rather than the >>less-similar 'libcrc32c'? Violates the Principle of Least Surprise >>;-) >> >> Jeff > > > The module under crypto is call "crc32c", which would conflict, UIASM. Fair enough... Jeff - 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/