Thread (23 messages) 23 messages, 4 authors, 2023-07-13

Re: [PATCH v2 18/18] fbdev: Document that framebuffer_alloc() returns zero'ed data

From: Randy Dunlap <hidden>
Date: 2023-07-13 16:03:15
Also in: amd-gfx, dri-devel, kvm, linux-arm-kernel, linux-hyperv, linux-input, linux-media, linux-omap, linux-sh, linux-staging, linuxppc-dev, lkml


On 7/13/23 06:21, Miguel Ojeda wrote:
On Thu, Jul 13, 2023 at 3:03 PM Thomas Zimmermann [off-list ref] wrote:
quoted
Most fbdev drivers depend on framebuffer_alloc() to initialize the
allocated memory to 0. Document this guarantee.

Suggested-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Helge Deller <deller@gmx.de>
Thanks for sending this! Maybe this would be best earlier in the
series, so that later patches make more sense (since they use the
guarantee), but it is not a big deal.
quoted
+ * aligned to sizeof(long). Both, the instance of struct fb_info and
+ * the driver private data, are cleared to zero.
I think both commas may be best omitted (but I am not a native speaker).
Yes, it would be better to omit them.
Reviewed-by: Miguel Ojeda <ojeda@kernel.org>

Cheers,
Miguel
-- 
~Randy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help