* Re: [PATCH] Fix comment style of `do_execveat_common()` [not found] <OS7PR01MB116815D7D0BCF55F3FE216293DFB32@OS7PR01MB11681.jpnprd01.prod.outlook.com> @ 2025-04-14 13:58 ` Jan Kara 2025-04-14 17:07 ` Matthew Wilcox 0 siblings, 1 reply; 2+ messages in thread From: Jan Kara @ 2025-04-14 13:58 UTC (permalink / raw) To: Cabbaken Q Cc: Kees Cook, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Alexander Viro, Christian Brauner, Jan Kara On Mon 14-04-25 07:07:57, Cabbaken Q wrote: > From 46fab5ecc860f26f790bec2a902a54bae58dfca7 Mon Sep 17 00:00:00 2001 > From: Ruoyu Qiu <cabbaken@outlook.com> > Date: Mon, 14 Apr 2025 14:56:28 +0800 > Subject: [PATCH] Fix comment style of `do_execveat_common()` > > Signed-off-by: Ruoyu Qiu <cabbaken@outlook.com> Thanks for the patch but I think fixing one extra space in a comment isn't really worth the effort of all the people involved in handling a patch. Honza > --- > fs/exec.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/exec.c b/fs/exec.c > index 8e4ea5f1e64c..51dad7af5083 100644 > --- a/fs/exec.c > +++ b/fs/exec.c > @@ -1903,7 +1903,7 @@ static int do_execveat_common(int fd, struct filename *filename, > /* > * We move the actual failure in case of RLIMIT_NPROC excess from > * set*uid() to execve() because too many poorly written programs > - * don't check setuid() return code. Here we additionally recheck > + * don't check setuid() return code. Here we additionally recheck > * whether NPROC limit is still exceeded. > */ > if ((current->flags & PF_NPROC_EXCEEDED) && > -- > 2.49.0 > > -- Jan Kara <jack@suse.com> SUSE Labs, CR ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Fix comment style of `do_execveat_common()` 2025-04-14 13:58 ` [PATCH] Fix comment style of `do_execveat_common()` Jan Kara @ 2025-04-14 17:07 ` Matthew Wilcox 0 siblings, 0 replies; 2+ messages in thread From: Matthew Wilcox @ 2025-04-14 17:07 UTC (permalink / raw) To: Jan Kara Cc: Cabbaken Q, Kees Cook, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Alexander Viro, Christian Brauner On Mon, Apr 14, 2025 at 03:58:37PM +0200, Jan Kara wrote: > On Mon 14-04-25 07:07:57, Cabbaken Q wrote: > > From 46fab5ecc860f26f790bec2a902a54bae58dfca7 Mon Sep 17 00:00:00 2001 > > From: Ruoyu Qiu <cabbaken@outlook.com> > > Date: Mon, 14 Apr 2025 14:56:28 +0800 > > Subject: [PATCH] Fix comment style of `do_execveat_common()` > > > > Signed-off-by: Ruoyu Qiu <cabbaken@outlook.com> > > Thanks for the patch but I think fixing one extra space in a comment isn't > really worth the effort of all the people involved in handling a patch. The correct number of spaces after a full stop is disputed. https://en.wikipedia.org/wiki/Sentence_spacing Do not send patches to adjust the number of spaces between sentences. You are wrong to change it. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-04-14 17:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <OS7PR01MB116815D7D0BCF55F3FE216293DFB32@OS7PR01MB11681.jpnprd01.prod.outlook.com>
2025-04-14 13:58 ` [PATCH] Fix comment style of `do_execveat_common()` Jan Kara
2025-04-14 17:07 ` Matthew Wilcox
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox