devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: dts: rockchip: replace gpio-key,wakeup with wakeup-source property
Date: Wed, 10 Feb 2016 09:51:32 +0000	[thread overview]
Message-ID: <56BB0824.2030900@arm.com> (raw)
In-Reply-To: <48510660.EJbbczq5fX@phil>



On 09/02/16 23:32, Heiko Stuebner wrote:
> Hi Sudeep,
>
> Am Montag, 8. Februar 2016, 21:55:12 schrieb Sudeep Holla:

[..]

>> Hi Heiko,
>>
>> You can reviewed this, however there are couple of ARM64 dts additions.
>> Also most of the other platform/SoC maintainers preferred to take it via
>> their tree and few of these got missed during v4.5 merge window.
>> Can you take it via your tree for v4.6 ?
>
> I've split the patch in two, as the 32 and 64 bit devicetree parts go
> through separate branches and applied both to their respective branches for
> v4.6

Thanks for splitting up the patch yourself.

-- 
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2016-02-10  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 21:55 [PATCH] ARM: dts: rockchip: replace gpio-key,wakeup with wakeup-source property Sudeep Holla
     [not found] ` <1454968512-11956-1-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2016-02-09 23:32   ` [PATCH] ARM: dts: rockchip: replace gpio-key, wakeup " Heiko Stuebner
2016-02-10  9:51     ` Sudeep Holla [this message]

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=56BB0824.2030900@arm.com \
    --to=sudeep.holla-5wv7dgnigg8@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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).