Messages in this thread | | | Subject | Re: [PATCH] lib/libcrc32c implementation | From | Clay Haapala <> | Date | Mon, 22 Mar 2004 11:27:39 -0600 |
| |
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.
I'd entertain any reasonable naming. For a bit, undercrypto, I was calling that module "crc32c_wrap", but that looked ugly, too, but probably is more PLS-compliant. :-) -- Clay Haapala (chaapala@cisco.com) Cisco Systems SRBU +1 763-398-1056 6450 Wedgwood Rd, Suite 130 Maple Grove MN 55311 PGP: C89240AD Of course the drugs advertised in all those emails are safe. Show me the dead spammers! (Please!) - 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/
| |