All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	jmorris@redhat.com, davem@davemloft.net, ak@suse.de,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [RFC][PATCH 2/4] AES assembler implementation for x86_64
Date: Mon, 18 Apr 2005 12:34:59 +0200	[thread overview]
Message-ID: <42638D53.9070809@domdv.de> (raw)
In-Reply-To: <200504181319.15708.vda@ilport.com.ua>

Denis Vlasenko wrote:
> On Monday 18 April 2005 12:01, Andreas Steinmetz wrote:
> 
>>Denis Vlasenko wrote:
>>
>>>On Sunday 17 April 2005 22:20, Andreas Steinmetz wrote:
>>>
>>>
>>>>The attached patch contains Gladman's in-kernel code for key schedule
>>>>and table generation modified to fit to my assembler implementation,
>>>>-- 
>>>>Andreas Steinmetz                       SPAMmers use robotrap@domdv.de
>>>
>>>
>>>Patch contains a mix of several coding styles:
>>> 
>>>+/*
>>>+ * #define byte(x, nr) ((unsigned char)((x) >> (nr*8))) 
>>>+ */
>>>+inline static u8
>>>+byte(const u32 x, const unsigned n)
>>>+{
>>>+       return x >> (n << 3);
>>>+}
>>>
>>>what does const do here?
>>
>>Taken 'as is' from current kernel sources, i,e, crypto/aes.c
> 
> 
> "It's a cut-n-paste" is not a good argument here. You
> are adding a _new file_ with your patch, it's okay to clean
> it up while doing this. IOW: do not dup the mess.
> 
> OTOH, if _exactly the same file_ exist in i384 arch, then
> you should not duplicate it at all. Find a way to use one file
> for both arches.
> 
> Note that this is only my view, I can be wrong.
> --
> vda
> 

I'll wait for Herbert Xu's review and his opinion on this.
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  reply	other threads:[~2005-04-18 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 19:20 [RFC][PATCH 2/4] AES assembler implementation for x86_64 Andreas Steinmetz
     [not found] ` <200504181118.50594.vda@ilport.com.ua>
2005-04-18  9:01   ` Andreas Steinmetz
2005-04-18 10:19     ` Denis Vlasenko
2005-04-18 10:34       ` Andreas Steinmetz [this message]
2005-04-18 12:33         ` 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=42638D53.9070809@domdv.de \
    --to=ast@domdv.de \
    --cc=ak@suse.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@ilport.com.ua \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.