From: Mike Rapoport <rppt@kernel.org>
To: Kushal Kothari <kushalkothari285@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mike.rapoport@gmail.com,
kushalkothari2850@gmail.com
Subject: Re: [PATCH v2] mm: Fix ERROR:do not initialise statics to 0 or NULL in memblock.c
Date: Wed, 3 Nov 2021 19:11:08 +0200 [thread overview]
Message-ID: <YYLCrAQnky9LM06s@kernel.org> (raw)
In-Reply-To: <20211103124523.10670-1-kushalkothari285@gmail.com>
Hi,
On Wed, Nov 03, 2021 at 06:15:23PM +0530, Kushal Kothari wrote:
> Subject: mm: Fix ERROR:do not initialise statics to 0 or NULL in memblock.c
Please use mm/memblock: or just memblock: prefix for memblock patches.
Besides, this patch does not fix a real error, it's only style fixup, so
"Fix ERROR" should be omitted here.
> The default value of static variable is zero and bool is false so
> not need to set it here.
> This patch fixes this ERROR in memblock.c
> Error found with checkpatch.pl.
Again, this is not a real error in the code but rather a coding style
inconsistency. Please update the changelog text to reflect this.
> Signed-off-by: Kushal Kothari <kushalkothari285@gmail.com>
> ---
>
> Changes in v2: Correct the subject line and remove <stdbool.h> which isn't
> necessary
>
> mm/memblock.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 5c3503c98b2f..9e2b7c1dbd03 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -152,10 +152,10 @@ static __refdata struct memblock_type *memblock_memory = &memblock.memory;
> } while (0)
>
> static int memblock_debug __initdata_memblock;
> -static bool system_has_some_mirror __initdata_memblock = false;
> +static bool system_has_some_mirror __initdata_memblock;
> static int memblock_can_resize __initdata_memblock;
> -static int memblock_memory_in_slab __initdata_memblock = 0;
> -static int memblock_reserved_in_slab __initdata_memblock = 0;
> +static int memblock_memory_in_slab __initdata_memblock;
> +static int memblock_reserved_in_slab __initdata_memblock;
>
> static enum memblock_flags __init_memblock choose_memblock_flags(void)
> {
> --
> 2.25.1
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2021-11-03 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 12:45 [PATCH v2] mm: Fix ERROR:do not initialise statics to 0 or NULL in memblock.c Kushal Kothari
2021-11-03 17:11 ` Mike Rapoport [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=YYLCrAQnky9LM06s@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kushalkothari2850@gmail.com \
--cc=kushalkothari285@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.rapoport@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.