From: Sudeep Holla <sudeep.holla@arm.com>
To: Michal Simek <michal.simek@xilinx.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH] arm64: dts: zynqmp: replace gpio-key,wakeup with wakeup-source property
Date: Mon, 5 Nov 2018 11:47:11 +0000 [thread overview]
Message-ID: <1a3fb47c-1427-d79e-9cb4-4476fd6a1cfb@arm.com> (raw)
In-Reply-To: <5f430204-9c97-0351-ff63-e64e8d42da69@xilinx.com>
On 05/11/2018 09:32, Michal Simek wrote:
> On 24. 10. 18 13:45, Sudeep Holla wrote:
>> Most of the legacy "gpio-key,wakeup" boolean property is already
>> replaced with "wakeup-source". However few occurrences of old property
>> has popped up again, probably from the remnants in downstream trees.
>>
>> This patch replaces the legacy properties with the unified
>> "wakeup-source" property.
>>
>
> Will be good to point to 700a38b27eefc which introduced but that's fine.
>
If you prefer, you can add the reference as you have already applied.
I am fine with that. Are you fine with 32-bit change ? I have posted
single patch covering multiple platforms so that I can ask ARM SoC to
pick it. If you can Ack it, I will ask them to pick directly.
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-11-05 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 11:45 [PATCH] ARM: dts: replace gpio-key, wakeup with wakeup-source property Sudeep Holla
2018-10-24 11:45 ` [PATCH] arm64: dts: zynqmp: " Sudeep Holla
2018-11-05 9:32 ` [PATCH] arm64: dts: zynqmp: replace gpio-key,wakeup " Michal Simek
2018-11-05 11:47 ` Sudeep Holla [this message]
2018-11-05 12:43 ` Michal Simek
2018-10-24 11:51 ` [PATCH] ARM: dts: " Alexandre Belloni
2018-10-24 12:03 ` [PATCH] ARM: dts: replace gpio-key, wakeup " Fabio Estevam
2018-10-24 13:43 ` [PATCH] ARM: dts: replace gpio-key,wakeup " Peter Rosin
2018-11-05 12:40 ` Michal Simek
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=1a3fb47c-1427-d79e-9cb4-4476fd6a1cfb@arm.com \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michal.simek@xilinx.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).