lkml.org 
[lkml]   [2012]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCHv3 07/16] OMAP: I2C: Optimise the remove code
    Date
    The omap_i2c_remove function may not be needed after
    device exit so the memory could be freed.

    Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
    ---
    drivers/i2c/busses/i2c-omap.c | 5 ++---
    1 files changed, 2 insertions(+), 3 deletions(-)

    diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
    index 7df1ea2..8515455 100644
    --- a/drivers/i2c/busses/i2c-omap.c
    +++ b/drivers/i2c/busses/i2c-omap.c
    @@ -1134,8 +1134,7 @@ err_release_region:
    return r;
    }

    -static int
    -omap_i2c_remove(struct platform_device *pdev)
    +static int __devexit omap_i2c_remove(struct platform_device *pdev)
    {
    struct omap_i2c_dev *dev = platform_get_drvdata(pdev);
    struct resource *mem;
    @@ -1228,7 +1227,7 @@ static struct dev_pm_ops omap_i2c_pm_ops = {

    static struct platform_driver omap_i2c_driver = {
    .probe = omap_i2c_probe,
    - .remove = omap_i2c_remove,
    + .remove = __devexit_p(omap_i2c_remove),
    .driver = {
    .name = "omap_i2c",
    .owner = THIS_MODULE,
    --
    1.7.1


    \
     
     \ /
      Last update: 2012-03-30 17:55    [W:0.021 / U:1.076 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site