18 Jan, 2021

1 commit


14 Dec, 2020

2 commits


12 Oct, 2020

1 commit


21 Jul, 2020

1 commit


23 May, 2020

1 commit

  • The current codebase makes use of the zero-length array language
    extension to the C90 standard, but the preferred mechanism to declare
    variable-length types such as these ones is a flexible array member[1][2],
    introduced in C99:

    struct foo {
    int stuff;
    struct boo array[];
    };

    By making use of the mechanism above, we will get a compiler warning
    in case the flexible array does not occur last in the structure, which
    will help us prevent some kind of undefined behavior bugs from being
    inadvertently introduced[3] to the codebase from now on.

    Also, notice that, dynamic memory allocations won't be affected by
    this change:

    "Flexible array members have incomplete type, and so the sizeof operator
    may not be applied. As a quirk of the original implementation of
    zero-length arrays, sizeof evaluates to zero."[1]

    sizeof(flexible-array-member) triggers a warning because flexible array
    members have incomplete type[1]. There are some instances of code in
    which the sizeof operator is being incorrectly/erroneously applied to
    zero-length arrays and the result is zero. Such instances may be hiding
    some bugs. So, this work (flexible-array member conversions) will also
    help to get completely rid of those sorts of issues.

    This issue was found with the help of Coccinelle.

    [1] https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html
    [2] https://github.com/KSPP/linux/issues/21
    [3] commit 76497732932f ("cxgb3/l2t: Fix undefined behaviour")

    Signed-off-by: Gustavo A. R. Silva
    Signed-off-by: Daniel Lezcano
    Link: https://lore.kernel.org/r/20200507192517.GA16557@embeddedor

    Gustavo A. R. Silva
     

23 Mar, 2020

2 commits

  • Fix below sparse warning:

    drivers/thermal/imx8mm_thermal.c:82:36: sparse: sparse: incorrect type in argument 2 (different address spaces), expected unsigned long const volatile *addr
    drivers/thermal/imx8mm_thermal.c:82:36: sparse: expected unsigned long const volatile *addr

    Signed-off-by: Anson Huang
    Signed-off-by: Daniel Lezcano
    Link: https://lore.kernel.org/r/1584973156-25734-1-git-send-email-Anson.Huang@nxp.com

    Anson Huang
     
  • i.MX8MP shares same TMU with i.MX8MM, the only difference is i.MX8MP
    has two thermal sensors while i.MX8MM ONLY has one, add multiple sensors
    support for i.MX8MM TMU driver.

    Signed-off-by: Anson Huang
    Signed-off-by: Daniel Lezcano
    Link: https://lore.kernel.org/r/1584674791-9717-2-git-send-email-Anson.Huang@nxp.com

    Anson Huang
     

12 Mar, 2020

1 commit