From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
Cc: akpm@linux-foundation.org, Liam.Howlett@oracle.com,
lorenzo.stoakes@oracle.com, vbabka@suse.cz, jannh@google.com,
pfalcato@suse.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: mmap: add missing space after comma in vma_expand_up macro
Date: Tue, 24 Mar 2026 11:07:07 +0000 [thread overview]
Message-ID: <738799c7-1087-4660-92d7-006b55938689@lucifer.local> (raw)
In-Reply-To: <20260324102909.26847-3-giorgitchankvetadze1997@gmail.com>
On Tue, Mar 24, 2026 at 02:29:11PM +0400, Giorgi Tchankvetadze wrote:
> Fix minor style inconsistency in macro parameter list to match
> kernel coding style.
>
> No functional change.
>
> Signed-off-by: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
This is fine as an early patch but as Pedro said we usualllly don't take these
unless you happen to be touching that bit of the code anyway (or code near it
etc.)
But it's fine so:
Reviewed-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
> ---
> mm/mmap.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 843160946aa5..37414e4ea362 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1001,12 +1001,12 @@ struct vm_area_struct *find_extend_vma_locked(struct mm_struct *mm, unsigned lon
>
> #if defined(CONFIG_STACK_GROWSUP)
>
> -#define vma_expand_up(vma,addr) expand_upwards(vma, addr)
> +#define vma_expand_up(vma, addr) expand_upwards(vma, addr)
> #define vma_expand_down(vma, addr) (-EFAULT)
>
> #else
>
> -#define vma_expand_up(vma,addr) (-EFAULT)
> +#define vma_expand_up(vma, addr) (-EFAULT)
> #define vma_expand_down(vma, addr) expand_downwards(vma, addr)
>
> #endif
> --
> 2.52.0
>
Cheers, Lorenzo
next prev parent reply other threads:[~2026-03-24 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 10:29 Giorgi Tchankvetadze
2026-03-24 10:45 ` Pedro Falcato
2026-03-24 11:07 ` Lorenzo Stoakes (Oracle) [this message]
2026-03-24 12:11 ` Giorgi Tchankvetadze
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=738799c7-1087-4660-92d7-006b55938689@lucifer.local \
--to=ljs@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=giorgitchankvetadze1997@gmail.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=vbabka@suse.cz \
/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