Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: get rid of useless label in btrfs_create_dio_extent()
Date: Tue, 7 Jul 2026 07:06:37 +0930	[thread overview]
Message-ID: <bf4ddfb6-6d8a-47af-b121-891fe7410078@gmx.com> (raw)
In-Reply-To: <74bcf9563b76639f84210fb5ee006d5a865280c0.1783338152.git.fdmanana@suse.com>



在 2026/7/6 21:14, fdmanana@kernel.org 写道:
> From: Filipe Manana <fdmanana@suse.com>
> 
> There's no point in having a label where under it we do nothing but return
> a variable. So remove it and directly return where we used to goto.
> 
> Signed-off-by: Filipe Manana <fdmanana@suse.com>

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> ---
>   fs/btrfs/direct-io.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/fs/btrfs/direct-io.c b/fs/btrfs/direct-io.c
> index 27d227f5bdc0..ed1779ccb4de 100644
> --- a/fs/btrfs/direct-io.c
> +++ b/fs/btrfs/direct-io.c
> @@ -150,7 +150,7 @@ static struct extent_map *btrfs_create_dio_extent(struct btrfs_inode *inode,
>   	if (type != BTRFS_ORDERED_NOCOW) {
>   		em = btrfs_create_io_em(inode, start, file_extent, type);
>   		if (IS_ERR(em))
> -			goto out;
> +			return em;
>   	}
>   
>   	ordered = btrfs_alloc_ordered_extent(inode, start, file_extent,
> @@ -167,7 +167,6 @@ static struct extent_map *btrfs_create_dio_extent(struct btrfs_inode *inode,
>   		ASSERT(!dio_data->ordered);
>   		dio_data->ordered = ordered;
>   	}
> - out:
>   
>   	return em;
>   }


      parent reply	other threads:[~2026-07-06 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 11:44 [PATCH] btrfs: get rid of useless label in btrfs_create_dio_extent() fdmanana
2026-07-06 15:19 ` Johannes Thumshirn
2026-07-06 21:36 ` Qu Wenruo [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=bf4ddfb6-6d8a-47af-b121-891fe7410078@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=fdmanana@kernel.org \
    --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