linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Li, Weigang" <weigang.li@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	"David S. Miller" <davem@davemloft.net>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Minchan Kim <minchan@kernel.org>,
	"Dan Streetman" <ddstreet@ieee.org>,
	<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 04/10] crypto/compress: add asynchronous compression support
Date: Thu, 4 Feb 2016 11:50:46 +0800	[thread overview]
Message-ID: <56B2CA96.4010104@intel.com> (raw)
In-Reply-To: <20160204032945.GA2100@gondor.apana.org.au>

On 2/4/2016 11:29 AM, Herbert Xu wrote:
> On Thu, Feb 04, 2016 at 11:28:50AM +0800, Herbert Xu wrote:
>> On Thu, Feb 04, 2016 at 11:25:27AM +0800, Li, Weigang wrote:
>>>
>>> Please can you advise how to get the acomp patch accepted?
>>
>> Can you do a posting of these patches without scomp so we can
>> evaluate the effects?
>
> Of course you can keep the driver-side scomp interface as otherwise
> the implementation would be unnecessarily complicated.
>
> Cheers,
>
Seems I need go back to my first acomp patch.. Assuming we shall still 
keep the comp i/f, and the linearisation of sg-list in acomp to fit the 
"comp" API? What do you mean by the driver-side scomp? Thanks!

  reply	other threads:[~2016-02-04  3:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  8:15 [PATCH v2 00/10] Introduce new async/sync compression APIs Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 01/10] crypto/compress: remove unused pcomp interface Joonsoo Kim
2016-01-27 14:17   ` Herbert Xu
2016-01-26  8:15 ` [PATCH v2 02/10] crypto: add algorithm type specific flag, CRYPTO_ALG_PRIVATE Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 03/10] crypto/compress: introduce sychronuous compression API Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 04/10] crypto/compress: add asynchronous compression support Joonsoo Kim
2016-01-27  7:41   ` Herbert Xu
2016-01-27  7:59     ` Li, Weigang
2016-01-27  8:03       ` Herbert Xu
2016-01-27  8:09         ` Herbert Xu
2016-01-27  8:26           ` Li, Weigang
2016-01-28  3:19           ` Joonsoo Kim
2016-01-29 10:09             ` Herbert Xu
2016-02-01  2:11               ` Joonsoo Kim
2016-02-04  3:25                 ` Li, Weigang
2016-02-04  3:28                   ` Herbert Xu
2016-02-04  3:29                     ` Herbert Xu
2016-02-04  3:50                       ` Li, Weigang [this message]
2016-02-04 14:56                         ` Herbert Xu
2016-02-04  7:17                     ` Joonsoo Kim
2016-02-04 14:53                       ` Herbert Xu
2016-02-04 16:19                         ` Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 05/10] crypto/lzo: support new compression APIs Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 06/10] crypto/lz4: " Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 07/10] crypto/lz4hc: " Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 08/10] crypto/842: " Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 09/10] crypto/deflate: " Joonsoo Kim
2016-01-26  8:15 ` [PATCH v2 10/10] crypto/testmgr: add new compression APIs test Joonsoo Kim

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=56B2CA96.4010104@intel.com \
    --to=weigang.li@intel.com \
    --cc=davem@davemloft.net \
    --cc=ddstreet@ieee.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky.work@gmail.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).