23 Dec, 2019

4 commits


18 Dec, 2019

13 commits


21 Aug, 2019

1 commit

  • My error handling "cleanup" was totally wrong. Both the "err" and "ret"
    variables are required. The "err" variable holds the error codes for
    rv3029_eeprom_enter/exit() and the "ret" variable holds the error codes
    for if actual write fails. In my patch if the write failed, the
    function probably still returned success.

    Reported-by: Tom Evans
    Fixes: 97f5b0379c38 ("rtc: rv3029: Clean up error handling in rv3029_eeprom_write()")
    Signed-off-by: Dan Carpenter
    Link: https://lore.kernel.org/r/20190817065604.GB29951@mwanda
    Signed-off-by: Alexandre Belloni

    Dan Carpenter
     

19 Jun, 2019

1 commit

  • Based on 2 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation #

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 4122 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Enrico Weigelt
    Reviewed-by: Kate Stewart
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

12 Oct, 2017

1 commit


26 Sep, 2017

1 commit


01 Sep, 2017

1 commit

  • i2c_device_id are not supposed to change at runtime. All functions
    working with i2c_device_id provided by work with
    const i2c_device_id. So mark the non-const structs as const.

    Signed-off-by: Arvind Yadav
    Signed-off-by: Alexandre Belloni

    Arvind Yadav
     

09 Mar, 2017

1 commit

  • The driver doesn't have a struct of_device_id table but supported devices
    are registered via Device Trees. This is working on the assumption that a
    I2C device registered via OF will always match a legacy I2C device ID and
    that the MODALIAS reported will always be of the form i2c:.

    But this could change in the future so the correct approach is to have an
    OF device ID table if the devices are registered via OF.

    Signed-off-by: Javier Martinez Canillas
    Signed-off-by: Alexandre Belloni

    Javier Martinez Canillas
     

21 May, 2016

8 commits


15 Mar, 2016

8 commits


04 Apr, 2014

1 commit