From: 郑伟 <wei.zheng@vivo.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Allison Randal <allison@lohutok.net>,
Hanjun Guo <guohanjun@huawei.com>,
Enrico Weigelt <info@metux.net>,
Yunfeng Ye <yeyunfeng@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
kernel@vivo.com, wenhu.wang@vivo.com
Subject: Re: [PATCH v2,RESEND] btrfs: fix the duplicated definition of 'inode_item_err'
Date: Mon, 16 Mar 2020 17:17:36 +0800 (GMT+08:00) [thread overview]
Message-ID: <AOAAuQCVCHmM4WW4PQrFj4rw.3.1584350256616.Hmail.wei.zheng@vivo.com> (raw)
In-Reply-To: <20200316082021.GA3146292@kroah.com>
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: 2020-03-16 16:20:21
To: Zheng Wei <wei.zheng@vivo.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,Will Deacon <will@kernel.org>,Chris Mason <clm@fb.com>,Josef Bacik <josef@toxicpanda.com>,David Sterba <dsterba@suse.com>,Allison Randal <allison@lohutok.net>,Hanjun Guo <guohanjun@huawei.com>,Enrico Weigelt <info@metux.net>,Yunfeng Ye <yeyunfeng@huawei.com>,Thomas Gleixner <tglx@linutronix.de>,linux-arm-kernel@lists.infradead.org,linux-kernel@vger.kernel.org,linux-btrfs@vger.kernel.org,kernel@vivo.com,wenhu.wang@vivo.com
Subject: Re: [PATCH v2,RESEND] btrfs: fix the duplicated definition of 'inode_item_err'>On Mon, Mar 16, 2020 at 11:45:57AM +0800, 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>
>> ---
>>
>> changelog
>> v1 -> v2
>> - resend for the failure of delivery to some recipients.
>>
>> fs/btrfs/tree-checker.c | 4 ----
>> 1 file changed, 4 deletions(-)
>
>Your choice of people to send this patch to is very odd:
>
>$ ./scripts/get_maintainer.pl --file fs/btrfs/tree-checker.c
>Chris Mason <clm@fb.com> (maintainer:BTRFS FILE SYSTEM)
>Josef Bacik <josef@toxicpanda.com> (maintainer:BTRFS FILE SYSTEM)
>David Sterba <dsterba@suse.com> (maintainer:BTRFS FILE SYSTEM)
>linux-btrfs@vger.kernel.org (open list:BTRFS FILE SYSTEM)
>linux-kernel@vger.kernel.org (open list)
>
so sorry for this,
as a new submitter, I used 'scripts/get_maintainer.pl my patch' command to get the mailing list.
I'll pay more attention next time.
Thanks,
Zheng Wei
>
>Please be more mindful.
>
>thanks,
>
>greg k-h
next prev parent reply other threads:[~2020-03-16 9:26 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 ` 郑伟 [this message]
2020-03-16 8:48 ` Nikolay Borisov
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=AOAAuQCVCHmM4WW4PQrFj4rw.3.1584350256616.Hmail.wei.zheng@vivo.com \
--to=wei.zheng@vivo.com \
--cc=allison@lohutok.net \
--cc=catalin.marinas@arm.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=info@metux.net \
--cc=josef@toxicpanda.com \
--cc=kernel@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wenhu.wang@vivo.com \
--cc=will@kernel.org \
--cc=yeyunfeng@huawei.com \
/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).