From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2,RESEND] btrfs: fix the duplicated definition of 'inode_item_err'
Date: Mon, 16 Mar 2020 10:48:45 +0200 [thread overview]
Message-ID: <ce6da077-787c-bae7-1b8a-7caa5ea879cb@suse.com> (raw)
In-Reply-To: <20200316034600.125962-1-wei.zheng@vivo.com>
On 16.03.20 г. 5:45 ч., Zheng Wei wrote:
> remove the duplicated definition of 'inode_item_err'
> in the file tree-checker.c
>
> Signed-off-by: Zheng Wei <wei.zheng@vivo.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
>
> changelog
> v1 -> v2
> - resend for the failure of delivery to some recipients.
>
> fs/btrfs/tree-checker.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/fs/btrfs/tree-checker.c b/fs/btrfs/tree-checker.c
> index a92f8a6dd192..517b44300a05 100644
> --- a/fs/btrfs/tree-checker.c
> +++ b/fs/btrfs/tree-checker.c
> @@ -957,10 +957,6 @@ static int check_dev_item(struct extent_buffer *leaf,
> return 0;
> }
>
> -/* Inode item error output has the same format as dir_item_err() */
> -#define inode_item_err(eb, slot, fmt, ...) \
> - dir_item_err(eb, slot, fmt, __VA_ARGS__)
> -
> static int check_inode_item(struct extent_buffer *leaf,
> struct btrfs_key *key, int slot)
> {
>
next prev parent reply other threads:[~2020-03-16 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 3:45 [PATCH v2,RESEND] btrfs: fix the duplicated definition of 'inode_item_err' Zheng Wei
2020-03-16 8:20 ` Greg Kroah-Hartman
2020-03-16 9:17 ` 郑伟
2020-03-16 8:48 ` Nikolay Borisov [this message]
2020-04-06 16:11 ` David Sterba
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=ce6da077-787c-bae7-1b8a-7caa5ea879cb@suse.com \
--to=nborisov@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).