From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 3BCEDC433EF for ; Thu, 19 May 2022 15:30:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240769AbiESPaX (ORCPT ); Thu, 19 May 2022 11:30:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51360 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235437AbiESPaR (ORCPT ); Thu, 19 May 2022 11:30:17 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABFB965A0 for ; Thu, 19 May 2022 08:30:16 -0700 (PDT) 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 dfw.source.kernel.org (Postfix) with ESMTPS id 51FA8618C2 for ; Thu, 19 May 2022 15:30:16 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3B708C34113; Thu, 19 May 2022 15:30:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1652974215; bh=tzRUqmBOG/j1qnFGl9Mf3VOLrKBnNATJIoMIm5y8DLU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=H62aCog291QEMK1cW22c3HyyS+7mpmPcZ5vI2yPWfGk5wrhlNzZr9I45Ox1FywU/l ZBijtlE6xiaZoRmzT65RGW2gXud9mnPHJsB+VQGv3GrScFWh4JhxTkieaJBZx3GpuM U2x5CMJ4opRjX80VkOo/96jrvYYhPr6tS+XiWBCptZWy3+hR3exmODHSPo2CYzQb5T GABJy/7V8QRvLXMp9SHwDQFK8Ueayf1/W4yLah8vAepLfYMHBiUtAbexd7wvLfnytC UpJEFgcH0jf021sqR+uD7oXfEWWvAOK4EiNlND8LdUhTSrvuAK1C97hQtzn2B258la RJoZJqzgzJnJw== Message-ID: <78b1e40e-69cd-465c-ee78-698eb38892be@kernel.org> Date: Thu, 19 May 2022 23:30:10 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH RESEND] f2fs: make f2fs_read_inline_data() more readable Content-Language: en-US To: Chao Liu , Jaegeuk Kim Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Yue Hu , Wayne Zhang , Chao Liu References: <20220519104010.2814819-1-chaoliu719@gmail.com> From: Chao Yu In-Reply-To: <20220519104010.2814819-1-chaoliu719@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/5/19 18:40, Chao Liu wrote: > From: Chao Liu > > In f2fs_read_inline_data(), it is confused with checking of > inline_data flag, as we checked it before calling. So this > patch add some comments for f2fs_has_inline_data(). > > Signed-off-by: Chao Liu Reviewed-by: Chao Yu Thanks,