linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Claudio Migliorelli <claudio.migliorelli@mail.polimi.it>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix some coding style errors in memblock.c
Date: Sun, 14 May 2023 12:46:22 +0300	[thread overview]
Message-ID: <ZGCt7hn9D114y0Ps@kernel.org> (raw)
In-Reply-To: <87r0sa7mm8.fsf@mail.polimi.it>

On Sun, Apr 23, 2023 at 03:29:35PM +0200, Claudio Migliorelli wrote:
> This patch removes the initialization of some static variables to 0 and
> `false` in the memblock source file, according to the coding style
> guidelines.
> 
> Signed-off-by: Claudio Migliorelli <claudio.migliorelli@mail.polimi.it>

Sorry for the delay.
Applied, thanks!

>  mm/memblock.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 25fd0626a9e7..6f0a2eda427c 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -156,10 +156,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.38.4
> 
> 

-- 
Sincerely yours,
Mike.


      reply	other threads:[~2023-05-14  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 13:29 Claudio Migliorelli
2023-05-14  9:46 ` 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=ZGCt7hn9D114y0Ps@kernel.org \
    --to=rppt@kernel.org \
    --cc=claudio.migliorelli@mail.polimi.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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