From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "hanyu001@208suo.com" <hanyu001@208suo.com>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"Liam.Howlett@Oracle.com" <Liam.Howlett@Oracle.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"willy@infradead.org" <willy@infradead.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: book3s32: add require space around that '?' and ':'
Date: Fri, 4 Aug 2023 16:02:14 +0000 [thread overview]
Message-ID: <1b4a2827-8cdb-92f4-e4fd-a8623d6bf7ce@csgroup.eu> (raw)
In-Reply-To: <44c1e39667c838d00c9dbb007184ccf1@208suo.com>
Hello,
Le 20/07/2023 à 09:34, hanyu001@208suo.com a écrit :
> Fix below checkpatch errors:
>
> ./arch/powerpc/mm/book3s32/tlb.c:102: ERROR: spaces required around that
> '?' (ctx:VxW)
> ./arch/powerpc/mm/book3s32/tlb.c:102: ERROR: spaces required around that
> ':' (ctx:VxW)
Can you please explain the purpose of those changes ? Do you use some
tools that get disturbed by such cosmetic errors ? Otherwise what is
your reason ?
We don't accept such standelone minor cosmetic changes at the first
place because it looks like a waste of time.
If you have major reasons to want those changes, please re-submit with a
details explanation in the commit message.
Thanks
Christophe
>
> Signed-off-by: Yu Han <hanyu001@208suo.com>
> ---
> arch/powerpc/mm/book3s32/tlb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/mm/book3s32/tlb.c
> b/arch/powerpc/mm/book3s32/tlb.c
> index 9ad6b56bfec9..de4abfe3d06b 100644
> --- a/arch/powerpc/mm/book3s32/tlb.c
> +++ b/arch/powerpc/mm/book3s32/tlb.c
> @@ -99,7 +99,7 @@ void hash__flush_tlb_page(struct vm_area_struct *vma,
> unsigned long vmaddr)
> struct mm_struct *mm;
> pmd_t *pmd;
>
> - mm = (vmaddr < TASK_SIZE)? vma->vm_mm: &init_mm;
> + mm = (vmaddr < TASK_SIZE) ? vma->vm_mm : &init_mm;
> pmd = pmd_off(mm, vmaddr);
> if (!pmd_none(*pmd))
> flush_hash_pages(mm->context.id, vmaddr, pmd_val(*pmd), 1);
prev parent reply other threads:[~2023-08-04 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_78C62F88E268136A2FCE91042CAB212A7709@qq.com>
2023-07-20 7:34 ` [PATCH] mm: book3s32: add require space around that '?' and ':' hanyu001
2023-08-04 16:02 ` Christophe Leroy [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=1b4a2827-8cdb-92f4-e4fd-a8623d6bf7ce@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=hanyu001@208suo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).