From: Keerthy <j-keerthy@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <tony@atomide.com>, <milo.kim@ti.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9] mfd: Remove redundant i2c_device_id
Date: Mon, 5 Jun 2017 20:07:37 +0530 [thread overview]
Message-ID: <e8cbe8fb-50fd-76ef-a5e3-59a7913622c5@ti.com> (raw)
In-Reply-To: <20170605103740.g4t3veigzpdzfkxi@dell>
On Monday 05 June 2017 04:07 PM, Lee Jones wrote:
> On Sun, 04 Jun 2017, Keerthy wrote:
>
>> 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.
>>
>> Keerthy (9):
>> mfd: tps65217: Remove redundant i2c_device_id
>> mfd: tps65218: Remove redundant i2c_device_id
>> mfd: palmas: Remove redundant i2c_device_id
>> mfd: lp873x: Remove redundant i2c_device_id
>> mfd: lp8788: Remove redundant i2c_device_id
>> mfd: lp3943: Remove redundant i2c_device_id
>> mfd: tps65086: Remove redundant i2c_device_id
>> mfd: tps65090: Remove redundant i2c_device_id
>> mfd: tps6586x: Remove redundant i2c_device_id
>>
>> drivers/mfd/lp3943.c | 11 ++---------
>> drivers/mfd/lp873x.c | 12 ++----------
>> drivers/mfd/lp8788.c | 11 ++---------
>> drivers/mfd/palmas.c | 15 ++-------------
>> drivers/mfd/tps65086.c | 12 ++----------
>> drivers/mfd/tps65090.c | 12 ++----------
>> drivers/mfd/tps65217.c | 14 +++-----------
>> drivers/mfd/tps65218.c | 9 +++++----
>> drivers/mfd/tps6586x.c | 12 ++----------
>
> Are all of these drivers DT only?
At least i did not find any platform code calling on to these drivers.
No dependency on OF as such. Hence sent these 9.
>
>> 9 files changed, 22 insertions(+), 86 deletions(-)
>
>
next prev parent reply other threads:[~2017-06-05 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 9:18 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 ` [PATCH 5/9] mfd: lp8788: " Keerthy
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 [this message]
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=e8cbe8fb-50fd-76ef-a5e3-59a7913622c5@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
all inboxes | Powered by JetHome®