[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <CR4C8V5T7751.HT9WYT9LB7X1@vincent-arch>
Date: Sun, 12 Mar 2023 11:38:31 +0100
From: "Vincenzo Palazzo" <vincenzopalazzodev@...il.com>
To: "Ivan Orlov" <ivan.orlov0322@...il.com>,
"David Kahurani" <k.kahurani@...il.com>
Cc: <lucho@...kov.net>, <ericvh@...il.com>, <asmadeus@...ewreck.org>,
<linux_oss@...debyte.com>, <linux-kernel@...r.kernel.org>,
<syzbot+cb1d16facb3cc90de5fb@...kaller.appspotmail.com>,
<v9fs-developer@...ts.sourceforge.net>,
<linux-kernel-mentees@...ts.linuxfoundation.org>
Subject: Re: [PATCH] 9P FS: Fix wild-memory-access write in v9fs_get_acl
On Sat Mar 11, 2023 at 6:35 PM CET, Ivan Orlov wrote:
>
> > I'm not sure what are the rules around here but I prefer to use brackets
> > more generously.
>
> I think in this particular case they can just make the code less
> readable (considering they will not change the behavior in any way).
> However, this is eternal discussion and I saw examples of both in the
> kernel sources.
Maybe this can be a good reading [1], I think it is more a kernel rule?
[1] https://www.kernel.org/doc/html/latest/process/coding-style.html
Cheers
Vincent.
> _______________________________________________
> Linux-kernel-mentees mailing list
> Linux-kernel-mentees@...ts.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Powered by blists - more mailing lists