Re: Input-evdev: Use kmalloc_array() in evdev_handle_get_val()
From: Dmitry Torokhov
Date: Sat Sep 24 2016 - 14:35:06 EST
On Sat, Sep 24, 2016 at 08:16:16PM +0200, SF Markus Elfring wrote:
> > So we have to multiply twice now, once in kmalloc_array, the second
> > time in memcpy().
> It looks so in the source code after the suggested refactoring.
> > No, thank you.
> Would you like to check any further if a specific compiler implementation
> will still optimise common subexpressions as you desired it?
> > Also, please note that we do not really treat the allocated "mem" as an array,
> > but rather area of memory that holds all bits that we need to transfer,
> > and so I consider using kmalloc_array() actually wrong here.
> Thanks for your explanation.
> > Please do not blindly follow checkpatch and coccinelle suggestions.
> > They are just that: suggestions and not hared rules.
> I am curious on how to clarify corresponding deviations further.
> Would you like to suggest any other details so that the evolving scripts
> can become better and safer for static source code analysis?
> Do you know any special properties which should be additionally checked
> at call sites which are similar to the discussed place?
If you are asking for some formal rules then no.
Again, what is the purpose of the changes? Are you working on the code
and the fact that the driver is older-style hinders your progress? Or
there are runtime improvements from your changes? Correctness issues?
I do not very much appreciate changes just to satisfy checkpatch rule