From: Andrzej Hajda <a.hajda@samsung.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-media@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Subject: Re: [PATCH RFC v2 1/2] max77693: added device tree support
Date: Wed, 17 Jul 2013 09:45:44 +0200 [thread overview]
Message-ID: <51E64BA8.30205@samsung.com> (raw)
In-Reply-To: <20130408152122.GU24058@zurbaran>
Hi Samuel,
A while ago I have send rebased patch adding device-tree support for
max77693 as you asked:
https://patchwork.kernel.org/patch/2414341/
The patch is still not applied. Is there a reason for that or just an
omission?
Regards
Andrzej
On 04/08/2013 05:21 PM, Samuel Ortiz wrote:
> Hi Andrzej,
>
> On Tue, Feb 19, 2013 at 04:36:16PM +0100, Andrzej Hajda wrote:
>> max77693 mfd main device uses only wakeup field
>> from max77693_platform_data. This field is mapped
>> to wakeup-source property in device tree.
>> Device tree bindings doc will be added in max77693-led patch.
>>
>> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
>> Reviewed-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>> ---
>> drivers/mfd/max77693.c | 40 +++++++++++++++++++++++++++++++++-------
>> 1 file changed, 33 insertions(+), 7 deletions(-)
> This patch looks good to me, but doesn't apply to mfd-next. Would you mind
> rebasing it ?
>
> Cheers,
> Samuel.
>
>
next prev parent reply other threads:[~2013-07-17 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 15:36 [PATCH RFC v2 0/2] max77693-led driver Andrzej Hajda
2013-02-19 15:36 ` [PATCH RFC v2 1/2] max77693: added device tree support Andrzej Hajda
2013-04-08 15:21 ` Samuel Ortiz
2013-07-17 7:45 ` Andrzej Hajda [this message]
2013-08-14 15:35 ` Andrzej Hajda
2013-08-14 16:04 ` Lee Jones
2013-02-19 15:36 ` [PATCH RFC v2 2/2] media: added max77693-led driver Andrzej Hajda
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=51E64BA8.30205@samsung.com \
--to=a.hajda@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sameo@linux.intel.com \
--cc=sw0312.kim@samsung.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).