Overall, it doesn't address any compiler warnings, but this is my first patch. I wanted to start with something concrete, and I saw an unsafe function and tried to fix it. The fact that the compilation behavior won't change is true, but the code will become a bit more formal — maybe that's a good thing.
пн, 1 июн. 2026 г. в 11:25, Andy Shevchenko <[email protected]>: > On Mon, Jun 1, 2026 at 3:44 AM Enchanted Hunter > <[email protected]> wrote: > > > > This patch replaces unsafe sprintf calls with snprintf in > > fbtft_register_framebuffer() to prevent potential buffer overflow. > > > > Signed-off-by: rat1bor <[email protected]> > > Does this change address any compiler warning or something like that? > At a glance I do not see any usefulness of this patch except an > unneeded churn. > > -- > With Best Regards, > Andy Shevchenko >
