From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id CD150C61D97
	for <linux-kernel@archiver.kernel.org>; Sun, 29 Jan 2023 18:12:29 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S235243AbjA2SM2 (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Sun, 29 Jan 2023 13:12:28 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37668 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229605AbjA2SM0 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 29 Jan 2023 13:12:26 -0500
Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5593A18B2F
        for <linux-kernel@vger.kernel.org>; Sun, 29 Jan 2023 10:12:26 -0800 (PST)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by ams.source.kernel.org (Postfix) with ESMTPS id 04749B80D1C
        for <linux-kernel@vger.kernel.org>; Sun, 29 Jan 2023 18:12:25 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 88EF6C433D2;
        Sun, 29 Jan 2023 18:12:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1675015943;
        bh=lsoELTbFCmklBSWaL0mK24RW1Go+2MZtjWOyil9mCl4=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=mW3FZyu5ZH+cxC7WR6UuMMMAN3q1AbaQsSx9+l+gmffmuquuvjwGBpbQbMjCQbMnG
         bBqVljJBriCJWAzg+VTsXo/kAm182A9LbGsoj3Do4rOzxxeZaXishWjfmzTcYJkW+1
         l68VMJ9BML7ydFtm8c/2CmsCGpqnKUkyCo5Zr65yxjy2FCIbygyQjBF6c617viNNHT
         X25fqJkTBZtfHuAiRN1KglOXfg4Fo1n6M2/r0TqgWga7U25wNHwJLchnsp53JkfluP
         zP/l3WcpXkYNRjak1Aq7bYbg0B4XXpq35xFa1OfAhZop4J/MvBwRr/RT+ZIdVL8bCT
         7tltXjP+Aaw1g==
Date:   Sun, 29 Jan 2023 10:12:21 -0800
From:   Eric Biggers <ebiggers@kernel.org>
To:     Chao Yu <chao@kernel.org>
Cc:     Yangtao Li <frank.li@vivo.com>, jaegeuk@kernel.org,
        linux-kernel@vger.kernel.org,
        linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/4] f2fs: fix to check lz4hc compression when
 CONFIG_F2FS_FS_LZ4HC is not enabled
Message-ID: <Y9a3BaVfBhvop4fp@sol.localdomain>
References: <20230124153346.74881-1-frank.li@vivo.com>
 <99e4e218-d9a4-93d1-c0d3-9ba01da21093@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <99e4e218-d9a4-93d1-c0d3-9ba01da21093@kernel.org>
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, Jan 29, 2023 at 06:21:17PM +0800, Chao Yu wrote:
> On 2023/1/24 23:33, Yangtao Li wrote:
> > f2fs supports lz4 compression algorithm and lz4hc compression algorithm,
> > which the level parameter needs to be passed in. When CONFIG_F2FS_FS_LZ4HC
> > is not enabled, even if there is no problem with the level parameter, add

lz4hc is not a different compression algorithm, but rather just a higher
compression level for lz4.

- Eric