Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752624AbdDDCSx (ORCPT ); Mon, 3 Apr 2017 22:18:53 -0400 Received: from mail-pg0-f65.google.com ([74.125.83.65]:33052 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751757AbdDDCSv (ORCPT ); Mon, 3 Apr 2017 22:18:51 -0400 Date: Tue, 4 Apr 2017 11:18:51 +0900 From: Sergey Senozhatsky To: Minchan Kim Cc: Andrew Morton , linux-kernel@vger.kernel.org, Sergey Senozhatsky , kernel-team@lge.com Subject: Re: [PATCH 3/5] zram: use zram_slot_lock instead of raw bit_spin_lock op Message-ID: <20170404021851.GB475@jagdpanzerIV.localdomain> References: <1491196653-7388-1-git-send-email-minchan@kernel.org> <1491196653-7388-4-git-send-email-minchan@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1491196653-7388-4-git-send-email-minchan@kernel.org> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 308 Lines: 10 On (04/03/17 14:17), Minchan Kim wrote: > With this clean-up phase, I want to use zram's wrapper function > to lock table access which is more consistent with other zram's > functions. > > Signed-off-by: Minchan Kim Reviewed-by: Sergey Senozhatsky -ss