02 Nov, 2017

1 commit


17 Aug, 2017

1 commit


01 Dec, 2015

1 commit


08 Nov, 2014

1 commit


27 Jun, 2014

1 commit


30 Jan, 2014

1 commit


22 Feb, 2013

1 commit

  • There is simply no reason to be manually setting the private driver
    data to NULL in the remove/fail to probe cases. This is just extra
    cruft code that can be removed.

    A few notes:
    * Nothing relies on drvdata being set to NULL.
    * The __device_release_driver() function eventually calls
    dev_set_drvdata(dev, NULL) anyway, so there's no need to do it
    twice.
    * I verified that there were no cases where xxx_get_drvdata() was
    being called in these drivers and checking for / relying on the NULL
    return value.

    This could be cleaned up kernel-wide but for now just take the baby
    step and remove from the i2c subsystem.

    Reported-by: Wolfram Sang
    Reported-by: Stephen Warren
    Signed-off-by: Doug Anderson
    Reviewed-by: Jean Delvare
    Acked-by: Peter Korsgaard
    Reviewed-by: Mika Westerberg
    Reviewed-by: Marek Vasut
    Signed-off-by: Wolfram Sang

    Doug Anderson
     

29 Jun, 2011

1 commit


19 Sep, 2009

1 commit


15 Jul, 2008

1 commit


30 Apr, 2008

1 commit

  • Based on earlier work by Jon Smirl and Jochen Friedrich.

    Update most new-style i2c drivers to use standard module aliasing
    instead of the old driver_name/type driver matching scheme. I've
    left the video drivers apart (except for SoC camera drivers) as
    they're a bit more diffcult to deal with, they'll have their own
    patch later.

    Signed-off-by: Jean Delvare
    Cc: Jon Smirl
    Cc: Jochen Friedrich

    Jean Delvare
     

12 Jul, 2007

1 commit