From: Lee Jones <lee.jones@linaro.org>
To: Keerthy <j-keerthy@ti.com>
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: Tue, 6 Jun 2017 08:17:03 +0100 [thread overview]
Message-ID: <20170606071703.o6dnzu4vjeywpoxn@dell> (raw)
In-Reply-To: <e8cbe8fb-50fd-76ef-a5e3-59a7913622c5@ti.com>
On Mon, 05 Jun 2017, Keerthy wrote:
>
>
> 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.
I can't accept these changes on any drivers which does not depend on
OF as a hard requirement.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-06-06 7:17 UTC|newest]
Thread overview: 31+ 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 ` Keerthy
2017-06-04 9:18 ` [PATCH 1/9] mfd: tps65217: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 2/9] mfd: tps65218: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 3/9] mfd: palmas: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 4/9] mfd: lp873x: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 5/9] mfd: lp8788: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 6/9] mfd: lp3943: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 7/9] mfd: tps65086: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 8/9] mfd: tps65090: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-04 9:18 ` [PATCH 9/9] mfd: tps6586x: " Keerthy
2017-06-04 9:18 ` Keerthy
2017-06-05 10:37 ` [PATCH 0/9] mfd: " Lee Jones
2017-06-05 14:37 ` Keerthy
2017-06-05 14:37 ` Keerthy
2017-06-06 7:17 ` Lee Jones [this message]
2017-06-06 7:30 ` Keerthy
2017-06-06 7:30 ` Keerthy
2017-06-06 7:48 ` Keerthy
2017-06-06 7:48 ` Keerthy
2017-06-06 10:44 ` Tony Lindgren
2017-06-06 11:01 ` Keerthy
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=20170606071703.o6dnzu4vjeywpoxn@dell \
--to=lee.jones@linaro.org \
--cc=j-keerthy@ti.com \
--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 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.