From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH] zram: cosmetic zram_bvec_write() cleanup
Date: Mon, 18 May 2015 23:00:59 +0900 [thread overview]
Message-ID: <20150518140059.GC3270@blaptop> (raw)
In-Reply-To: <1431864033-7111-1-git-send-email-sergey.senozhatsky@gmail.com>
On Sun, May 17, 2015 at 09:00:33PM +0900, Sergey Senozhatsky wrote:
> `bool locked' local variable tells us if we should perform
> zcomp_strm_release() or not (jumped to `out' label before
> zcomp_strm_find() occurred), which is equivalent to `zstrm'
> being or not being NULL. remove `locked' and check `zstrm'
> instead.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Acked-by: Minchan Kim <minchan@kernel.org>
--
Kind regards,
Minchan Kim
prev parent reply other threads:[~2015-05-18 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 12:00 [PATCH] zram: cosmetic zram_bvec_write() cleanup Sergey Senozhatsky
2015-05-18 14:00 ` Minchan Kim [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=20150518140059.GC3270@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--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