mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: "Li, Weigang" <weigang.li@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Minchan Kim <minchan@kernel.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/7] Introduce new async/sync compression APIs
Date: Wed, 13 Jan 2016 16:29:27 +0800	[thread overview]
Message-ID: <20160113082927.GA8655@gondor.apana.org.au> (raw)
In-Reply-To: <20160113083134.GA6966@js1304-P5Q-DELUXE>

On Wed, Jan 13, 2016 at 05:31:34PM +0900, Joonsoo Kim wrote:
>
> Herbert, for you, is it better to send it after merge window?

Yes that would be very much appreciated.

Thanks,
-- 
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

      reply	other threads:[~2016-01-13  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04  4:46 Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 1/7] crypto/compress: remove unused pcomp interface Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 2/7] crypto/compress: introduce sychronuous compression API Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 3/7] crypto: add asynchronous compression support Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 4/7] crypto/lzo: support SCOMPRESS alg type Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 5/7] crypto: testmgr: add scompress/acompress test Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 6/7] crypto/compress: add algorithm type specific flag, DECOMP_NOCTX Joonsoo Kim
2016-01-04  4:46 ` [PATCH RFC 7/7] crypto/lzo: add CRYPTO_ALG_SCOMPRESS_DECOMP_NOCTX cra_flags Joonsoo Kim
2016-01-12  8:00 ` [PATCH RFC 0/7] Introduce new async/sync compression APIs Li, Weigang
2016-01-12 12:47   ` Herbert Xu
2016-01-13  8:31     ` Joonsoo Kim
2016-01-13  8:29       ` Herbert Xu [this message]

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=20160113082927.GA8655@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --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 \
    --cc=weigang.li@intel.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

all inboxes | Powered by JetHome®