From: Lukas Czerner <lczerner@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@dilger.ca>
Subject: Re: [e2fsprogs PATCH] libext2fs: remove unused variable in ext2fs_xattrs_read_inode()
Date: Wed, 4 Jan 2023 11:23:26 +0100 [thread overview]
Message-ID: <20230104102326.eoitvoj3bbcp6oqd@fedora> (raw)
In-Reply-To: <20230104090314.276028-1-ebiggers@kernel.org>
On Wed, Jan 04, 2023 at 01:03:14AM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Address the following compiler warning with gcc -Wall:
>
> ext_attr.c: In function ‘ext2fs_xattrs_read_inode’:
> ext_attr.c:1000:16: warning: unused variable ‘i’ [-Wunused-variable]
> 1000 | size_t i;
> | ^
You might as well remove the unnecessary newline at the top of the
function.
But regardless, you can add.
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
Thanks!
-Lukas
>
> Cc: Andreas Dilger <adilger@dilger.ca>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> lib/ext2fs/ext_attr.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/lib/ext2fs/ext_attr.c b/lib/ext2fs/ext_attr.c
> index d36fe68d..6fc4214c 100644
> --- a/lib/ext2fs/ext_attr.c
> +++ b/lib/ext2fs/ext_attr.c
> @@ -997,7 +997,6 @@ errcode_t ext2fs_xattrs_read_inode(struct ext2_xattr_handle *handle,
> unsigned int storage_size;
> char *start, *block_buf = NULL;
> blk64_t blk;
> - size_t i;
> errcode_t err = 0;
>
> EXT2_CHECK_MAGIC(handle, EXT2_ET_MAGIC_EA_HANDLE);
> --
> 2.39.0
>
prev parent reply other threads:[~2023-01-04 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 9:03 [e2fsprogs PATCH] libext2fs: remove unused variable in ext2fs_xattrs_read_inode() Eric Biggers
2023-01-04 10:23 ` Lukas Czerner [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=20230104102326.eoitvoj3bbcp6oqd@fedora \
--to=lczerner@redhat.com \
--cc=adilger@dilger.ca \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@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