From: Herbert Xu <herbert@gondor.apana.org.au>
To: abed mohammad kamaluddin <abedamu@gmail.com>
Cc: linux-crypto@vger.kernel.org,
"akamaluddin@cavium.com" <akamaluddin@cavium.com>,
pathreya@cavium.com, mchalla@cavium.com
Subject: Re: [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support ***
Date: Thu, 20 Apr 2017 16:00:38 +0800 [thread overview]
Message-ID: <20170420080038.GB6780@gondor.apana.org.au> (raw)
In-Reply-To: <CACVarEQ9kW=zF+Zse17LA2KjM-dg7mb6d5XWCvSbg5nCT3=Y6A@mail.gmail.com>
On Thu, Apr 20, 2017 at 12:39:58PM +0530, abed mohammad kamaluddin wrote:
> Hi Herbert,
>
> > I think we should convert ipcomp over to the new interface first
> > in order to make sure that we don't need to change the interface
> > which would be hard to do once we export it to user-space.
>
> Would it be acceptable if we export an algif interface using alg_type_compress,
> which is being used by ipcomp currently? We would like to use our zip
> device from
> userspace through this interface.
No we're not going to export an obsolete interface.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2017-04-20 8:01 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
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 [this message]
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=20170420080038.GB6780@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=abedamu@gmail.com \
--cc=akamaluddin@cavium.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mchalla@cavium.com \
--cc=pathreya@cavium.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 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.