From: Herbert Xu <herbert@gondor.apana.org.au>
To: Denis Cheng <crquan@gmail.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
dengxw@163.com, Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH] [RESEND] crypto test: use print_hex_dump from <linux/kernel.h> instead
Date: Tue, 27 Nov 2007 09:05:50 +0800 [thread overview]
Message-ID: <20071127010550.GB447@gondor.apana.org.au> (raw)
In-Reply-To: <1196098095-8995-1-git-send-email-crquan@gmail.com>
On Tue, Nov 27, 2007 at 01:28:15AM +0800, Denis Cheng wrote:
> this patch is against cryptodev-2.6, and have passed scripts/checkpatch.pl
>
> KERN_DEBUG is stripped out, this acts more like the original in tcrypto.c
>
> and the last parameter "bool ascii" set to zero to disable ascii output,
> this could keep it happy on Unicode terminals.
>
> Cc: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: Denis Cheng <crquan@gmail.com>
Sorry, it still doesn't compile because it doesn't change test_aead.
Perhaps you need to pull cryptodev again?
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2007-11-27 1:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 7:13 [PATCH 1/2] crypto test: use print_hex_dump from <linux/kernel.h> Denis Cheng
2007-11-26 14:39 ` Herbert Xu
2007-11-26 17:28 ` [PATCH] [RESEND] crypto test: use print_hex_dump from <linux/kernel.h> instead Denis Cheng
2007-11-26 18:01 ` Joe Perches
2007-11-27 1:35 ` Herbert Xu
2007-11-27 2:47 ` [PATCH] [RESEND] crypto test: use print_hex_dump from kernel.h instead Denis Cheng
2007-11-27 2:58 ` Richard Knutsson
2007-11-27 5:03 ` rae l
2007-11-27 9:26 ` Andrew Morton
2007-11-29 11:13 ` Herbert Xu
2007-11-30 1:20 ` rae l
2007-11-30 6:00 ` Herbert Xu
2007-11-27 1:05 ` Herbert Xu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071127010550.GB447@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=crquan@gmail.com \
--cc=dengxw@163.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).