public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amitoj Kaur Chawla <amitoj1606@gmail.com>
To: rpurdie@rpsys.net, j.anaszewski@samsung.com,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: julia.lawall@lip6.fr
Subject: [PATCH 0/7] leds: Use devm_led_classdev_register
Date: Mon, 7 Mar 2016 20:20:47 +0530	[thread overview]
Message-ID: <cover.1457355135.git.amitoj1606@gmail.com> (raw)

Switch to resource-managed function devm_led_classdev_register instead
of led_classdev_register and remove unneeded led_classdev_unregister.

The Coccinelle semantic patch used to make this change is as follows:
//<smpl>
@platform@
identifier p, probefn, removefn;
@@
struct platform_driver p = {
  .probe = probefn,
  .remove = removefn,
};

@prb@
identifier platform.probefn, pdev;
expression e;
@@
probefn(struct platform_device *pdev, ...) {
  ...
  e =
- led_classdev_register
+ devm_led_classdev_register
  (...);
   ...
?- led_classdev_unregister(...);
  ...
}
@remove depends on prb@
identifier platform.removefn;
@@
removefn(...) {
...
?- led_classdev_unregister(...);
...
}
//</smpl>

Amitoj Kaur Chawla (7):
  leds: 88pm860x: Use devm_led_classdev_register
  leds: lp8788: Use devm_led_classdev_register
  leds: wm381x-status: Use devm_led_classdev_register
  leds: s3c24xx: Use devm_led_classdev_register
  leds: da903x: Use devm_led_classdev_register
  leds: max8997: Use devm_led_classdev_register
  leds: lm3533: Use devm_led_classdev_register

 drivers/leds/leds-88pm860x.c      | 11 +----------
 drivers/leds/leds-da903x.c        | 11 +----------
 drivers/leds/leds-lm3533.c        | 12 +++---------
 drivers/leds/leds-lp8788.c        | 12 +-----------
 drivers/leds/leds-max8997.c       | 12 +-----------
 drivers/leds/leds-s3c24xx.c       | 12 +-----------
 drivers/leds/leds-wm831x-status.c | 12 +-----------
 7 files changed, 9 insertions(+), 73 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-03-07 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 14:50 Amitoj Kaur Chawla [this message]
2016-03-07 14:50 ` [PATCH 1/7] leds: 88pm860x: Use devm_led_classdev_register Amitoj Kaur Chawla
2016-03-07 14:51 ` [PATCH 2/7] leds: lp8788: " Amitoj Kaur Chawla
2016-03-07 14:51 ` [PATCH 3/7] leds: wm381x-status: " Amitoj Kaur Chawla
2016-03-07 14:51 ` [PATCH 4/7] leds: s3c24xx: " Amitoj Kaur Chawla
2016-03-07 14:51 ` [PATCH 5/7] leds: da903x: " Amitoj Kaur Chawla
2016-03-07 14:51 ` [PATCH 6/7] leds: max8997: " Amitoj Kaur Chawla
2016-03-07 14:51 ` [PATCH 7/7] leds: lm3533: " Amitoj Kaur Chawla
2016-03-08  8:26 ` [PATCH 0/7] leds: " Jacek Anaszewski
2016-03-08 12:42   ` Amitoj Kaur Chawla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1457355135.git.amitoj1606@gmail.com \
    --to=amitoj1606@gmail.com \
    --cc=j.anaszewski@samsung.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox