From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 13/19] ARM: dts: tegra: replace legacy *,wakeup property with wakeup-source
Date: Tue, 15 Dec 2015 16:35:42 +0000 [thread overview]
Message-ID: <5670415E.6000208@arm.com> (raw)
In-Reply-To: <1445422216-29375-14-git-send-email-sudeep.holla@arm.com>
On 21/10/15 11:10, Sudeep Holla wrote:
> Though the keyboard and other driver will continue to support the legacy
> "gpio-key,wakeup", "nvidia,wakeup-source" boolean property to enable the
> wakeup source, "wakeup-source" is the new standard binding.
>
> This patch replaces all the legacy wakeup properties with the unified
> "wakeup-source" property in order to avoid any futher copy-paste
> duplication.
>
Ping, do you prefer taking via your tree or should I send to armsoc
directly ?
--
Regards,
Sudeep
next prev parent reply other threads:[~2015-12-15 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445422216-29375-1-git-send-email-sudeep.holla@arm.com>
2015-10-21 10:10 ` [PATCH 06/19] input: tegra-kbc: enable support for the standard "wakeup-source" property Sudeep Holla
[not found] ` <1445422216-29375-7-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2015-10-23 6:39 ` Dmitry Torokhov
2015-10-23 10:23 ` Sudeep Holla
2015-10-26 8:33 ` Dmitry Torokhov
2015-10-21 10:10 ` [PATCH 13/19] ARM: dts: tegra: replace legacy *,wakeup property with wakeup-source Sudeep Holla
2015-12-15 16:35 ` Sudeep Holla [this message]
[not found] ` <1445422216-29375-14-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2015-12-23 11:24 ` Sudeep Holla
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=5670415E.6000208@arm.com \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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).