linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Muchun Song <songmuchun@bytedance.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: shmem: make shmem_init return void
Date: Tue, 29 Mar 2022 10:12:26 +0800	[thread overview]
Message-ID: <67fb3ff7-f46a-985d-94ac-698885eb43c5@huawei.com> (raw)
In-Reply-To: <CAMZfGtXccwgR6TxNJc6aYV+WGJvAWWAz=RXEHNWDwjKfV49JuA@mail.gmail.com>

On 2022/3/28 22:50, Muchun Song wrote:
> On Mon, Mar 28, 2022 at 7:44 PM Miaohe Lin <linmiaohe@huawei.com> wrote:
>>
>> The return value of shmem_init is never used. So we can make it
>> return void now.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>>  include/linux/shmem_fs.h | 2 +-
>>  mm/shmem.c               | 9 ++++-----
>>  2 files changed, 5 insertions(+), 6 deletions(-)
>>
>> diff --git a/include/linux/shmem_fs.h b/include/linux/shmem_fs.h
>> index ab51d3cd39bd..3e915cc550bc 100644
>> --- a/include/linux/shmem_fs.h
>> +++ b/include/linux/shmem_fs.h
>> @@ -56,7 +56,7 @@ static inline struct shmem_inode_info *SHMEM_I(struct inode *inode)
>>   * Functions in mm/shmem.c called directly from elsewhere:
>>   */
>>  extern const struct fs_parameter_spec shmem_fs_parameters[];
>> -extern int shmem_init(void);
>> +extern void shmem_init(void);
>>  extern int shmem_init_fs_context(struct fs_context *fc);
>>  extern struct file *shmem_file_setup(const char *name,
>>                                         loff_t size, unsigned long flags);
>> diff --git a/mm/shmem.c b/mm/shmem.c
>> index 529c9ad3e926..26e09a022087 100644
>> --- a/mm/shmem.c
>> +++ b/mm/shmem.c
>> @@ -3879,7 +3879,7 @@ static struct file_system_type shmem_fs_type = {
>>         .fs_flags       = FS_USERNS_MOUNT,
>>  };
>>
>> -int __init shmem_init(void)
>> +void __init shmem_init(void)
>>  {
>>         int error;
>>
>> @@ -3904,14 +3904,13 @@ int __init shmem_init(void)
>>         else
>>                 shmem_huge = SHMEM_HUGE_NEVER; /* just in case it was patched */
>>  #endif
>> -       return 0;
>> +       return;
>>
>>  out1:
>>         unregister_filesystem(&shmem_fs_type);
>>  out2:
>>         shmem_destroy_inodecache();
>>         shm_mnt = ERR_PTR(error);
>> -       return error;
>>  }
>>
>>  #if defined(CONFIG_TRANSPARENT_HUGEPAGE) && defined(CONFIG_SYSFS)
>> @@ -3989,14 +3988,14 @@ static struct file_system_type shmem_fs_type = {
>>         .fs_flags       = FS_USERNS_MOUNT,
>>  };
>>
>> -int __init shmem_init(void)
>> +void __init shmem_init(void)
>>  {
>>         BUG_ON(register_filesystem(&shmem_fs_type) != 0);
>>
>>         shm_mnt = kern_mount(&shmem_fs_type);
>>         BUG_ON(IS_ERR(shm_mnt));
>>
>> -       return 0;
>> +       return;
> 
> Weird. Using return at the end of a void function.

Thanks for review. And thanks Andrew for kindly fixing this. :)

> .
> 



      reply	other threads:[~2022-03-29  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 11:27 Miaohe Lin
2022-03-28 14:50 ` Muchun Song
2022-03-29  2:12   ` Miaohe Lin [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=67fb3ff7-f46a-985d-94ac-698885eb43c5@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=songmuchun@bytedance.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