Thread (15 messages) 15 messages, 4 authors, 2024-03-04

Re: [PATCH v2 5/9] mm: Initialize struct vm_unmapped_area_info

From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Date: 2024-02-28 17:02:03
Also in: linux-alpha, linux-arm-kernel, linux-mips, linux-mm, linux-s390, linux-sh, lkml, loongarch, sparclinux

On Wed, 2024-02-28 at 13:22 +0000, Christophe Leroy wrote:
quoted
Any preference? Or maybe am I missing your point and talking
nonsense?
So my preference would go to the addition of:

        info.new_field = 0;

But that's very minor and if you think it is easier to manage and 
maintain by performing {} initialisation at declaration, lets go for
that.
Appreciate the clarification and help getting this right. I'm thinking
Kees' and now Kirill's point about this patch resulting in unnecessary
manual zero initialization of the structs is probably something that
needs to be addressed.

If I created a bunch of patches to change each call site, I think the
the best is probably to do the designated field zero initialization
way.

But I can do something for powerpc special if you want. I'll first try
with powerpc matching the others, and if it seems objectionable, please
let me know.

Thanks,

Rick
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help