From: Chao Yu <chao@kernel.org>
To: Gao Xiang <gaoxiang25@huawei.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid the global name 'fault_name'
Date: Sun, 1 Jul 2018 10:25:23 +0800 [thread overview]
Message-ID: <c00e7a33-ca80-283b-be88-88e0adf5cbfc@kernel.org> (raw)
In-Reply-To: <174b5d84-8d41-4b8e-4e87-39f8cc3948ae@huawei.com>
On 2018/7/1 0:06, Gao Xiang wrote:
>
> Oh, I just found the same patch written by Chao at:
> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev
>
> I just fixed the erofs name conflicts, so fixed f2fs as well.
> Please ignore this one.
I didn't send it out, I think merging yours will be fine to me. :)
Thanks,
>
> Thanks,
> Gao Xiang
>
> On 2018/6/30 23:57, Gao Xiang wrote:
>> Non-prefix global name 'fault_name' will pollute global
>> namespace, fix it.
>>
>> Refer to:
>> https://lists.01.org/pipermail/kbuild-all/2018-June/049660.html
>>
>> To: Jaegeuk Kim <jaegeuk@kernel.org>
>> To: Chao Yu <yuchao0@huawei.com>
>> Cc: linux-f2fs-devel@lists.sourceforge.net
>> Cc: linux-kernel@vger.kernel.org
>> Reported-by: kbuild test robot <lkp@intel.com>
>> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
>> ---
>> fs/f2fs/f2fs.h | 4 ++--
>> fs/f2fs/super.c | 2 +-
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
>> index 4d8b1de..11a2e09 100644
>> --- a/fs/f2fs/f2fs.h
>> +++ b/fs/f2fs/f2fs.h
>> @@ -65,7 +65,7 @@ struct f2fs_fault_info {
>> unsigned int inject_type;
>> };
>>
>> -extern char *fault_name[FAULT_MAX];
>> +extern char *f2fs_fault_name[FAULT_MAX];
>> #define IS_FAULT_SET(fi, type) ((fi)->inject_type & (1 << (type)))
>> #endif
>>
>> @@ -1279,7 +1279,7 @@ struct f2fs_sb_info {
>> #ifdef CONFIG_F2FS_FAULT_INJECTION
>> #define f2fs_show_injection_info(type) \
>> printk("%sF2FS-fs : inject %s in %s of %pF\n", \
>> - KERN_INFO, fault_name[type], \
>> + KERN_INFO, f2fs_fault_name[type], \
>> __func__, __builtin_return_address(0))
>> static inline bool time_to_inject(struct f2fs_sb_info *sbi, int type)
>> {
>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> index 3995e92..df12dcd 100644
>> --- a/fs/f2fs/super.c
>> +++ b/fs/f2fs/super.c
>> @@ -41,7 +41,7 @@
>>
>> #ifdef CONFIG_F2FS_FAULT_INJECTION
>>
>> -char *fault_name[FAULT_MAX] = {
>> +char *f2fs_fault_name[FAULT_MAX] = {
>> [FAULT_KMALLOC] = "kmalloc",
>> [FAULT_KVMALLOC] = "kvmalloc",
>> [FAULT_PAGE_ALLOC] = "page alloc",
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
next prev parent reply other threads:[~2018-07-01 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 15:57 [PATCH] f2fs: avoid the global name 'fault_name' Gao Xiang
2018-06-30 16:06 ` Gao Xiang
2018-07-01 2:25 ` Chao Yu [this message]
2018-07-01 2:23 ` [f2fs-dev] " Chao Yu
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=c00e7a33-ca80-283b-be88-88e0adf5cbfc@kernel.org \
--to=chao@kernel.org \
--cc=gaoxiang25@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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).