public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sergey.senozhatsky@gmail.com,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Minchan Kim <minchan@kernel.org>,
	mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: + zram-switch-to-crypto-compress-api.patch added to -mm tree
Date: Wed, 1 Jun 2016 10:26:32 +0900	[thread overview]
Message-ID: <20160601012632.GE461@swordfish> (raw)
In-Reply-To: <574de1b2.LDeSluXYR1Ke9MvG%akpm@linux-foundation.org>

On (05/31/16 12:10), akpm@linux-foundation.org wrote:
> The patch titled
>      Subject: zram: switch to crypto compress API
> has been added to the -mm tree.  Its filename is
>      zram-switch-to-crypto-compress-api.patch
> 
> This patch should soon appear at
>     http://ozlabs.org/~akpm/mmots/broken-out/zram-switch-to-crypto-compress-api.patch
> and later at
>     http://ozlabs.org/~akpm/mmotm/broken-out/zram-switch-to-crypto-compress-api.patch

Andrew,

I'd prefer this patch to also include changes from this one:
http://ozlabs.org/~akpm/mmots/broken-out/zram-align-zcomp-interface-to-crypto-comp-api.patch
(http://article.gmane.org/gmane.linux.kernel/2231316)

(per Minchan).

IOW, squash
  http://ozlabs.org/~akpm/mmots/broken-out/zram-switch-to-crypto-compress-api.patch
 and
  http://ozlabs.org/~akpm/mmots/broken-out/zram-align-zcomp-interface-to-crypto-comp-api.patch


what's the best way to do it? should I resend the series?

	-ss

       reply	other threads:[~2016-06-01  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <574de1b2.LDeSluXYR1Ke9MvG%akpm@linux-foundation.org>
2016-06-01  1:26 ` Sergey Senozhatsky [this message]
2016-06-01  2:01   ` + zram-switch-to-crypto-compress-api.patch added to -mm tree Andrew Morton
2016-06-01  2:09     ` Sergey Senozhatsky

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=20160601012632.GE461@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=sergey.senozhatsky@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