Hi.
On Mon, 2005-07-11 at 09:14, Christoph Hellwig wrote:
> Please send new crytptoapi algorithms to the cryptoapi maintainers for review.
> It's something that's completely independent of any software suspend stuff.
Thanks.
Did this about a week prior to sending the patches. Sorry - including
Hi.
On Mon, 2005-07-11 at 09:14, Christoph Hellwig wrote:
Please send new crytptoapi algorithms to the cryptoapi maintainers for review.
It's something that's completely independent of any software suspend stuff.
Thanks.
Did this about a week prior to sending the patches. Sorry - including
Please send new crytptoapi algorithms to the cryptoapi maintainers for review.
It's something that's completely independent of any software suspend stuff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Please send new crytptoapi algorithms to the cryptoapi maintainers for review.
It's something that's completely independent of any software suspend stuff.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Howdy.
On Sat, 2005-07-09 at 22:10, Pavel Machek wrote:
> BTW if it is "contributed code", you may want original contributor to
> push it, so that you don't have to do all the lindenting/cleaning/etc
> yourself.
It is, and he's gone to ground. As requested by Pekka, I've Lindented
it. Apart from
Hi!
> +/*
> + * sacrifice some compression quality in favour of compression speed.
> + * (roughly 1-2% worse compression for large blocks and
> + * 9-10% for small, redundant, blocks and >>20% better speed in both cases)
> + * In short: enable this for binary data, disable this for text data.
> +
Hi!
+/*
+ * sacrifice some compression quality in favour of compression speed.
+ * (roughly 1-2% worse compression for large blocks and
+ * 9-10% for small, redundant, blocks and 20% better speed in both cases)
+ * In short: enable this for binary data, disable this for text data.
+ */
Howdy.
On Sat, 2005-07-09 at 22:10, Pavel Machek wrote:
BTW if it is contributed code, you may want original contributor to
push it, so that you don't have to do all the lindenting/cleaning/etc
yourself.
It is, and he's gone to ground. As requested by Pekka, I've Lindented
it. Apart from
Hi.
Thanks very much for all your reading and commenting. I really
appreciate it. By the way, you do want replies sent to both addresses?
This one is contributed code. I haven't had or needed an update since it
was added though, so I guess I could reindent it. Will do.
Regards,
Nigel
On Wed,
On 7/6/05, Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> diff -ruNp 625-crypto-api-work.patch-old/crypto/lzf.c
> 625-crypto-api-work.patch-new/crypto/lzf.c
> --- 625-crypto-api-work.patch-old/crypto/lzf.c 1970-01-01 10:00:00.0
> +1000
> +++ 625-crypto-api-work.patch-new/crypto/lzf.c
On 7/6/05, Nigel Cunningham [EMAIL PROTECTED] wrote:
diff -ruNp 625-crypto-api-work.patch-old/crypto/lzf.c
625-crypto-api-work.patch-new/crypto/lzf.c
--- 625-crypto-api-work.patch-old/crypto/lzf.c 1970-01-01 10:00:00.0
+1000
+++ 625-crypto-api-work.patch-new/crypto/lzf.c
Hi.
Thanks very much for all your reading and commenting. I really
appreciate it. By the way, you do want replies sent to both addresses?
This one is contributed code. I haven't had or needed an update since it
was added though, so I guess I could reindent it. Will do.
Regards,
Nigel
On Wed,
diff -ruNp 625-crypto-api-work.patch-old/crypto/Kconfig
625-crypto-api-work.patch-new/crypto/Kconfig
--- 625-crypto-api-work.patch-old/crypto/Kconfig2005-06-20
11:46:49.0 +1000
+++ 625-crypto-api-work.patch-new/crypto/Kconfig2005-07-04
23:14:19.0 +1000
@@ -262,6
diff -ruNp 625-crypto-api-work.patch-old/crypto/Kconfig
625-crypto-api-work.patch-new/crypto/Kconfig
--- 625-crypto-api-work.patch-old/crypto/Kconfig2005-06-20
11:46:49.0 +1000
+++ 625-crypto-api-work.patch-new/crypto/Kconfig2005-07-04
23:14:19.0 +1000
@@ -262,6
14 matches
Mail list logo
