All of lore.kernel.org
 help / color / mirror / Atom feed
From: abed mohammad kamaluddin <abedamu@gmail.com>
To: "Stephan Müller" <smueller@chronox.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org,
	"akamaluddin@cavium.com" <akamaluddin@cavium.com>,
	pathreya@cavium.com, mchalla@cavium.com
Subject: Re: [RFC PATCH v1 1/1] crypto: algif_compression - User-space interface for compression
Date: Fri, 21 Apr 2017 21:37:48 +0530	[thread overview]
Message-ID: <CACVarETBrCPZjEOABBQTKR52Wjv3bHxA_wg66hMDw2fNrtZmsA@mail.gmail.com> (raw)
In-Reply-To: <1869148.qqR7Ib7PBA@tauon.chronox.de>

On Fri, Apr 21, 2017 at 9:20 PM, Stephan Müller <smueller@chronox.de> wrote:
> Am Freitag, 21. April 2017, 17:42:10 CEST schrieb abed mohammad kamaluddin:
>
> Just diff the just RFCed algif_kpp with the proposed patch set for
> algif_skcipher and algif_aead. There you will see that 80% of all code is
> identical (if you disregard the different namespace). And that is the code I
> am referring to.
>
> Ciao
> Stephan

Thanks, I will use the pointer. Considering all the identical code,
the proposal to consolidate would definitely help!

Thanks,
Abed

  reply	other threads:[~2017-04-21 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 18:34 [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support *** Abed Kamaluddin
2017-04-13 18:34 ` [RFC PATCH v1 1/1] crypto: algif_compression - User-space interface for compression Abed Kamaluddin
2017-04-14  4:19   ` PrasannaKumar Muralidharan
2017-04-17  1:31   ` Eric Biggers
2017-04-18 10:12   ` Stephan Müller
2017-04-21 15:42     ` abed mohammad kamaluddin
2017-04-21 15:50       ` Stephan Müller
2017-04-21 16:07         ` abed mohammad kamaluddin [this message]
2017-04-14  8:32 ` [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support *** Herbert Xu
2017-04-20  7:09   ` abed mohammad kamaluddin
2017-04-20  8:00     ` Herbert Xu
2017-04-20 14:39       ` abed mohammad kamaluddin

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=CACVarETBrCPZjEOABBQTKR52Wjv3bHxA_wg66hMDw2fNrtZmsA@mail.gmail.com \
    --to=abedamu@gmail.com \
    --cc=akamaluddin@cavium.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mchalla@cavium.com \
    --cc=pathreya@cavium.com \
    --cc=smueller@chronox.de \
    /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.