From: "Adrian-Ken Rüegsegger" <rueegsegger@swiss-it.ch>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
Date: Mon, 19 May 2008 23:24:32 +0200 [thread overview]
Message-ID: <4831F010.5020202@swiss-it.ch> (raw)
In-Reply-To: <20080519205944.GC16813@Chamillionaire.breakpoint.cc>
Sebastian Siewior wrote:
> * Adrian-Ken R?egsegger | 2008-05-19 22:37:31 [+0200]:
>> Sebastian Siewior wrote:
>>> * Adrian-Ken Rueegsegger | 2008-05-18 23:35:55 [+0200]:
>>>> Sebastian, would you be so kind to test this patch on PowerPC?
>>> Acked-by: Sebastian Siewior <sebastian@breakpoint.cc>
>> Sebastian, thanks for testing :)
> You welcome.
> Any particular reason why named it rmd... instead of ripemd...?
Looking at other crypto modules like tgr192 or wp512 I got the impression that names should
be kept short.
>> If there are no objections I will prepare patches for the other RIPEMD modules and submit all of them in one patch set.
> Any objections on moving ripemd.h from include/crypto into crypto?
Not from my side. I put it there because the SHA header file is in the same place.
-Adrian
> Herbert?
> Since you only use it within crypto/ and you don't need it in userspace
> or arch/ I would prefer to have it in crypto.
>
>> -Adrian
> Sebastian
next prev parent reply other threads:[~2008-05-19 21:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 20:07 [PATCH] crypto: rmd128: make it work on my prefered architecture Sebastian Siewior
2008-05-17 8:10 ` [PATCH v2] " Sebastian Siewior
2008-05-17 8:20 ` Sebastian Siewior
2008-05-17 8:22 ` David Miller
2008-05-17 8:27 ` Sebastian Siewior
2008-05-17 8:37 ` Herbert Xu
2008-05-17 8:47 ` Sebastian Siewior
2008-05-17 9:01 ` David Miller
2008-05-17 9:14 ` Sebastian Siewior
2008-05-17 9:55 ` David Miller
2008-05-17 9:56 ` Herbert Xu
2008-05-21 2:47 ` David Miller
2008-05-21 7:09 ` Sebastian Siewior
2008-05-21 7:11 ` David Miller
2008-05-21 7:20 ` Sebastian Siewior
2008-05-21 7:36 ` David Miller
2008-05-26 11:05 ` Herbert Xu
2008-05-27 11:37 ` David Miller
2008-05-29 8:44 ` Sebastian Siewior
2008-06-02 20:17 ` Sebastian Siewior
2008-06-03 0:00 ` Herbert Xu
2008-05-18 21:35 ` [PATCH] [CRYPTO] rmd128: Fix endian problems Adrian-Ken Rueegsegger
2008-05-18 22:01 ` Sebastian Siewior
2008-05-19 20:01 ` Sebastian Siewior
2008-05-19 20:37 ` Adrian-Ken Rüegsegger
2008-05-19 20:59 ` Sebastian Siewior
2008-05-19 21:24 ` Adrian-Ken Rüegsegger [this message]
2008-05-20 2:28 ` Herbert Xu
2008-05-20 3:42 ` Herbert Xu
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=4831F010.5020202@swiss-it.ch \
--to=rueegsegger@swiss-it.ch \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
/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