From: Sudeep Holla <sudeep.holla@arm.com>
To: Peter Rosin <peda@axentia.se>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: at91: replace gpio-key,wakeup with wakeup-source property
Date: Fri, 28 Dec 2018 13:25:57 +0000 [thread overview]
Message-ID: <20181228132557.GA12018@e107155-lin> (raw)
In-Reply-To: <c22dacbe-ddc9-04c7-cda8-100dcbe0e70b@axentia.se>
On Fri, Dec 21, 2018 at 06:46:12PM +0000, Peter Rosin wrote:
> On 2018-12-21 19:11, Sudeep Holla wrote:
> > Most of the legacy "gpio-key,wakeup" property are already replaced
> > with "wakeup-source". However few occurrences of old property has
> > popped up again, probably from the remnants in downstream trees.
> > Almost all of those were remove couple of years back.
> >
> > Replace the legacy properties with the unified "wakeup-source"
> > property introduced in the commit 700a38b27eef ("Input: gpio_keys -
> > switch to using generic device properties")
> >
> > Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > Cc: Peter Rosin <peda@axentia.se>
> > Cc: Nicolas Ferre <nicolas.ferre@microchip.com>
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>
> Why is this not v3?
> Why did you drop all the tags you already got?
>
Sorry for that, I intentionally dropped Acks from maintainer who would
merge and add their sign-offs, but I dropped yours accidentally.
> Acked-by: Peter Rosin <peda@axentia.se>
>
Thanks.
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-12-28 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 18:11 [PATCH] ARM: dts: at91: replace gpio-key, wakeup with wakeup-source property Sudeep Holla
2018-12-21 18:46 ` [PATCH] ARM: dts: at91: replace gpio-key,wakeup " Peter Rosin
2018-12-28 13:25 ` Sudeep Holla [this message]
2019-01-08 18:13 ` Alexandre Belloni
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=20181228132557.GA12018@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peda@axentia.se \
/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).