From: Masahiro Yamada <yamada.masahiro@socionext.com> To: Philipp Zabel <p.zabel@pengutronix.de> Cc: linux-arm-kernel@lists.infradead.org, Masahiro Yamada <yamada.masahiro@socionext.com>, linux-kernel@vger.kernel.org Subject: [PATCH 4/7] reset: pistachio: use devm_reset_controller_register() Date: Sun, 1 May 2016 19:37:00 +0900 [thread overview] Message-ID: <1462099023-11819-5-git-send-email-yamada.masahiro@socionext.com> (raw) In-Reply-To: <1462099023-11819-1-git-send-email-yamada.masahiro@socionext.com> Use devm_reset_controller_register() for the reset controller registration and drop the .remove callback. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> --- drivers/reset/reset-pistachio.c | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/drivers/reset/reset-pistachio.c b/drivers/reset/reset-pistachio.c index 72a97a1..bbc4c06 100644 --- a/drivers/reset/reset-pistachio.c +++ b/drivers/reset/reset-pistachio.c @@ -121,16 +121,7 @@ static int pistachio_reset_probe(struct platform_device *pdev) rd->rcdev.ops = &pistachio_reset_ops; rd->rcdev.of_node = np; - return reset_controller_register(&rd->rcdev); -} - -static int pistachio_reset_remove(struct platform_device *pdev) -{ - struct pistachio_reset_data *data = platform_get_drvdata(pdev); - - reset_controller_unregister(&data->rcdev); - - return 0; + return devm_reset_controller_register(dev, &rd->rcdev); } static const struct of_device_id pistachio_reset_dt_ids[] = { @@ -141,7 +132,6 @@ MODULE_DEVICE_TABLE(of, pistachio_reset_dt_ids); static struct platform_driver pistachio_reset_driver = { .probe = pistachio_reset_probe, - .remove = pistachio_reset_remove, .driver = { .name = "pistachio-reset", .of_match_table = pistachio_reset_dt_ids, -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: yamada.masahiro@socionext.com (Masahiro Yamada) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 4/7] reset: pistachio: use devm_reset_controller_register() Date: Sun, 1 May 2016 19:37:00 +0900 [thread overview] Message-ID: <1462099023-11819-5-git-send-email-yamada.masahiro@socionext.com> (raw) In-Reply-To: <1462099023-11819-1-git-send-email-yamada.masahiro@socionext.com> Use devm_reset_controller_register() for the reset controller registration and drop the .remove callback. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> --- drivers/reset/reset-pistachio.c | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/drivers/reset/reset-pistachio.c b/drivers/reset/reset-pistachio.c index 72a97a1..bbc4c06 100644 --- a/drivers/reset/reset-pistachio.c +++ b/drivers/reset/reset-pistachio.c @@ -121,16 +121,7 @@ static int pistachio_reset_probe(struct platform_device *pdev) rd->rcdev.ops = &pistachio_reset_ops; rd->rcdev.of_node = np; - return reset_controller_register(&rd->rcdev); -} - -static int pistachio_reset_remove(struct platform_device *pdev) -{ - struct pistachio_reset_data *data = platform_get_drvdata(pdev); - - reset_controller_unregister(&data->rcdev); - - return 0; + return devm_reset_controller_register(dev, &rd->rcdev); } static const struct of_device_id pistachio_reset_dt_ids[] = { @@ -141,7 +132,6 @@ MODULE_DEVICE_TABLE(of, pistachio_reset_dt_ids); static struct platform_driver pistachio_reset_driver = { .probe = pistachio_reset_probe, - .remove = pistachio_reset_remove, .driver = { .name = "pistachio-reset", .of_match_table = pistachio_reset_dt_ids, -- 1.9.1
next prev parent reply other threads:[~2016-05-01 10:39 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-01 10:36 [PATCH 0/7] reset: add managned reset_controller_register() Masahiro Yamada 2016-05-01 10:36 ` Masahiro Yamada 2016-05-01 10:36 ` [PATCH 1/7] reset: add devm_reset_controller_register API Masahiro Yamada 2016-05-01 10:36 ` Masahiro Yamada 2016-05-03 10:07 ` Laxman Dewangan 2016-05-03 10:07 ` Laxman Dewangan 2016-05-03 10:17 ` Philipp Zabel 2016-05-03 10:17 ` Philipp Zabel 2016-05-03 10:26 ` Masahiro Yamada 2016-05-03 10:26 ` Masahiro Yamada 2016-05-03 11:41 ` Masahiro Yamada 2016-05-03 11:41 ` Masahiro Yamada 2016-05-03 14:20 ` Philipp Zabel 2016-05-03 14:20 ` Philipp Zabel 2016-05-01 10:36 ` [PATCH 2/7] reset: ath79: use devm_reset_controller_register() Masahiro Yamada 2016-05-01 10:36 ` Masahiro Yamada 2016-05-01 10:36 ` [PATCH 3/7] reset: lpc18xx: " Masahiro Yamada 2016-05-01 10:36 ` Masahiro Yamada 2016-05-01 21:04 ` Joachim Eastwood 2016-05-01 21:04 ` Joachim Eastwood 2016-05-02 8:26 ` Philipp Zabel 2016-05-02 8:26 ` Philipp Zabel 2016-05-02 15:52 ` Masahiro Yamada 2016-05-02 15:52 ` Masahiro Yamada 2016-05-03 9:05 ` Philipp Zabel 2016-05-03 9:05 ` Philipp Zabel 2016-05-03 10:25 ` Masahiro Yamada 2016-05-03 10:25 ` Masahiro Yamada 2016-05-03 11:08 ` Philipp Zabel 2016-05-03 11:08 ` Philipp Zabel 2016-05-03 11:40 ` Masahiro Yamada 2016-05-03 11:40 ` Masahiro Yamada 2016-05-01 10:37 ` Masahiro Yamada [this message] 2016-05-01 10:37 ` [PATCH 4/7] reset: pistachio: " Masahiro Yamada 2016-05-01 10:37 ` [PATCH 5/7] reset: sunxi: " Masahiro Yamada 2016-05-01 10:37 ` Masahiro Yamada 2016-05-01 10:37 ` [PATCH 6/7] reset: socfpga: " Masahiro Yamada 2016-05-01 10:37 ` Masahiro Yamada 2016-05-01 10:37 ` [PATCH 7/7] reset: zynq: " Masahiro Yamada 2016-05-01 10:37 ` Masahiro Yamada
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=1462099023-11819-5-git-send-email-yamada.masahiro@socionext.com \ --to=yamada.masahiro@socionext.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=p.zabel@pengutronix.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.