From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 0/6] part3 trivial adjustments for return variable coding style
Date: Fri, 24 May 2024 11:09:23 +0800 [thread overview]
Message-ID: <d007c586-58e0-4391-8466-e7f615daaa88@oracle.com> (raw)
In-Reply-To: <20240523171825.GF17126@twin.jikos.cz>
On 5/24/24 01:18, David Sterba wrote:
> On Tue, May 21, 2024 at 08:10:03PM +0200, David Sterba wrote:
>> On Wed, May 22, 2024 at 01:11:06AM +0800, Anand Jain wrote:
>>> This is v4 of part 3 of the series, containing renaming with optimization of the
>>> return variable.
>>>
>>> v3 part3:
>>> https://lore.kernel.org/linux-btrfs/cover.1715783315.git.anand.jain@oracle.com/
>>> v2 part2:
>>> https://lore.kernel.org/linux-btrfs/cover.1713370756.git.anand.jain@oracle.com/
>>> v1:
>>> https://lore.kernel.org/linux-btrfs/cover.1710857863.git.anand.jain@oracle.com/
>>>
>>> Anand Jain (6):
>>> btrfs: rename err to ret in btrfs_cleanup_fs_roots()
>>> btrfs: rename ret to err in btrfs_recover_relocation()
>>> btrfs: rename ret to ret2 in btrfs_recover_relocation()
>>> btrfs: rename err to ret in btrfs_recover_relocation()
>>> btrfs: rename err to ret in btrfs_drop_snapshot()
>>> btrfs: rename err to ret in btrfs_find_orphan_roots()
>>
>> 1-5 look ok to me, for patch 6 there's the ret = 0 reset question sent
>> to v3.
>
> You can add 1-5 to for-next with
>
> Reviewed-by: David Sterba <dsterba@suse.com>
>
Pushed 1-5.
> and only resend 6.
IMO, in the patch 6, the
if (ret > 1)
ret = 0;
section is already simple and typical for the ret > 1 cases.
Could you pls check my response in v3.
Thanks, Anand
prev parent reply other threads:[~2024-05-24 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 17:11 [PATCH v4 0/6] part3 trivial adjustments for return variable coding style Anand Jain
2024-05-21 17:11 ` [PATCH v4 1/6] btrfs: rename err to ret in btrfs_cleanup_fs_roots() Anand Jain
2024-05-21 17:11 ` [PATCH v4 2/6] btrfs: rename ret to err in btrfs_recover_relocation() Anand Jain
2024-05-21 17:11 ` [PATCH v4 3/6] btrfs: rename ret to ret2 " Anand Jain
2024-05-21 17:11 ` [PATCH v4 4/6] btrfs: rename err to ret " Anand Jain
2024-05-21 17:11 ` [PATCH v4 5/6] btrfs: rename err to ret in btrfs_drop_snapshot() Anand Jain
2024-05-21 17:11 ` [PATCH v4 6/6] btrfs: rename err to ret in btrfs_find_orphan_roots() Anand Jain
2024-05-21 18:10 ` [PATCH v4 0/6] part3 trivial adjustments for return variable coding style David Sterba
2024-05-23 17:18 ` David Sterba
2024-05-24 3:09 ` Anand Jain [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=d007c586-58e0-4391-8466-e7f615daaa88@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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