From: Laxman Dewangan <ldewangan@nvidia.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
<linux-kernel@vger.kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 0/4] mfd: max77686: Remove unneeded non-OF code in driver
Date: Thu, 12 Jan 2017 21:52:40 +0530 [thread overview]
Message-ID: <5877AD50.6010902@nvidia.com> (raw)
In-Reply-To: <1484228857-20182-1-git-send-email-javier@osg.samsung.com>
On Thursday 12 January 2017 07:17 PM, Javier Martinez Canillas wrote:
> Hello Lee,
>
> This series contains cleanups for the max77686 PMIC MFD driver.
> The driver is only used in DT platforms and so all the code
> related with the i2c_device_id table can be removed.
>
> Best regards,
> Javier
>
>
LGTM, let me also review the max77620 on similar cleanups.
Acked-by: Laxman Dewangan <ldewangan@nvidia.com>
prev parent reply other threads:[~2017-01-12 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:47 [PATCH 0/4] mfd: max77686: Remove unneeded non-OF code in driver Javier Martinez Canillas
2017-01-12 13:47 ` [PATCH 1/4] mfd: max77686: Don't attempt to get i2c_device_id .data Javier Martinez Canillas
2017-01-13 12:56 ` Krzysztof Kozlowski
2017-01-23 11:32 ` Lee Jones
2017-01-12 13:47 ` [PATCH 2/4] mfd: max77686: Use of_device_get_match_data() helper Javier Martinez Canillas
2017-01-13 13:04 ` Krzysztof Kozlowski
2017-01-13 13:12 ` Javier Martinez Canillas
2017-01-12 13:47 ` [PATCH 3/4] mfd: max77686: Use the struct i2c_driver .probe_new instead of .probe Javier Martinez Canillas
2017-01-13 13:11 ` Krzysztof Kozlowski
2017-01-12 13:47 ` [PATCH 4/4] mfd: max77686: Remove I2C device ID table Javier Martinez Canillas
2017-01-13 13:13 ` Krzysztof Kozlowski
2017-01-12 16:22 ` Laxman Dewangan [this message]
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=5877AD50.6010902@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=javier@osg.samsung.com \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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.