From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers
Date: Thu, 12 Dec 2013 14:20:17 -0700 [thread overview]
Message-ID: <52AA2891.2020502@wwwdotorg.org> (raw)
In-Reply-To: <1386855064-10993-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 12/12/2013 06:31 AM, Laxman Dewangan wrote:
> ams AS3722 is the system power manager module IC for the Tegra124 based
> Venice2 platform. Enable configs for gpio, pincontrol, rtc, regulator
> support from this device.
I've squashed patch 1/2 into Tegra's for-3.14/defconfig branch.
I've applied patch 2/2 to Tegra's for-3.14/dt branch.
next prev parent reply other threads:[~2013-12-12 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 13:31 [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers Laxman Dewangan
2013-12-12 13:31 ` [PATCH 2/2] ARM: tegra: add ams AS3722 device to Venice2 DT Laxman Dewangan
[not found] ` <1386855064-10993-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-12 21:20 ` Stephen Warren [this message]
[not found] ` <52AA2891.2020502-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-12 21:51 ` [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers Stephen Warren
[not found] ` <52AA2FD1.3020000-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-13 6:24 ` Laxman Dewangan
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=52AA2891.2020502@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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).