From: Keerthy <j-keerthy@ti.com>
To: <tony@atomide.com>, <milo.kim@ti.com>, <lee.jones@linaro.org>
Cc: <j-keerthy@ti.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 5/9] mfd: lp8788: Remove redundant i2c_device_id
Date: Sun, 4 Jun 2017 14:48:40 +0530 [thread overview]
Message-ID: <1496567924-4278-6-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1496567924-4278-1-git-send-email-j-keerthy@ti.com>
With the introduction of probe_new function the i2c_device_id
is no longer needed. Hence the remove the same and use probe_new
instead of probe.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
Compile tested.
drivers/mfd/lp8788.c | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/mfd/lp8788.c b/drivers/mfd/lp8788.c
index acf6165..a46139d 100644
--- a/drivers/mfd/lp8788.c
+++ b/drivers/mfd/lp8788.c
@@ -170,7 +170,7 @@ static int lp8788_platform_init(struct lp8788 *lp)
.max_register = MAX_LP8788_REGISTERS,
};
-static int lp8788_probe(struct i2c_client *cl, const struct i2c_device_id *id)
+static int lp8788_probe(struct i2c_client *cl)
{
struct lp8788 *lp;
struct lp8788_platform_data *pdata = dev_get_platdata(&cl->dev);
@@ -212,19 +212,12 @@ static int lp8788_remove(struct i2c_client *cl)
return 0;
}
-static const struct i2c_device_id lp8788_ids[] = {
- {"lp8788", 0},
- { }
-};
-MODULE_DEVICE_TABLE(i2c, lp8788_ids);
-
static struct i2c_driver lp8788_driver = {
.driver = {
.name = "lp8788",
},
- .probe = lp8788_probe,
+ .probe_new = lp8788_probe,
.remove = lp8788_remove,
- .id_table = lp8788_ids,
};
static int __init lp8788_init(void)
--
1.9.1
next prev parent reply other threads:[~2017-06-04 9:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 9:18 [PATCH 0/9] mfd: Remove redundant i2c_device_id Keerthy
2017-06-04 9:18 ` [PATCH 1/9] mfd: tps65217: " Keerthy
2017-06-04 9:18 ` [PATCH 2/9] mfd: tps65218: " Keerthy
2017-06-04 9:18 ` [PATCH 3/9] mfd: palmas: " Keerthy
2017-06-04 9:18 ` [PATCH 4/9] mfd: lp873x: " Keerthy
2017-06-04 9:18 ` Keerthy [this message]
2017-06-04 9:18 ` [PATCH 6/9] mfd: lp3943: " Keerthy
2017-06-04 9:18 ` [PATCH 7/9] mfd: tps65086: " Keerthy
2017-06-04 9:18 ` [PATCH 8/9] mfd: tps65090: " Keerthy
2017-06-04 9:18 ` [PATCH 9/9] mfd: tps6586x: " Keerthy
2017-06-05 10:37 ` [PATCH 0/9] mfd: " Lee Jones
2017-06-05 14:37 ` Keerthy
2017-06-06 7:17 ` Lee Jones
2017-06-06 7:30 ` Keerthy
2017-06-06 7:48 ` Keerthy
2017-06-06 10:44 ` Tony Lindgren
2017-06-06 11:01 ` Keerthy
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=1496567924-4278-6-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).