Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Krzysztof Kozlowski
	<k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Kukjin Kim <kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source
Date: Wed, 16 Dec 2015 10:32:56 +0000	[thread overview]
Message-ID: <56713DD8.1050001@arm.com> (raw)
In-Reply-To: <5670A2F2.5060009-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>



On 15/12/15 23:32, Krzysztof Kozlowski wrote:
> On 16.12.2015 01:35, Sudeep Holla wrote:
>>
>>
>> On 21/10/15 11:10, Sudeep Holla wrote:
>>> Though the keyboard and other driver will continue to support the legacy
>>> "gpio-key,wakeup", "linux-keypad,wakeup" 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.
>>>
>>> Cc: Kukjin Kim <kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>>> Cc: Krzysztof Kozlowski <k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>>
>> Ping, do you prefer taking via your tree or should I send to armsoc
>> directly ?
>
> Usually it depends on the dependencies... but:
> 1. I just received this patch - 12/19.

Sorry for that. The initial idea was to show all the changes but merge
the binding and dependencies first, so didn't cc all.

> 2. No cover letter, no other patches, no explanation about any
> dependencies or other related changes. Nothing. Just one patch.

Yes this was initially posted as part of the series, but only
dependencies were merged for v4.4

> 3. The patch mentions new standard binding. Was the new binding already
> merged? Or is it part of these series? What about backward compatibility?

Not a brand new binding, but made existing one a standard so that we
don't continue to be creative and generate more bindings for the same
thing. Yes binding and dependent patches are already in mainline. And
yes backward compatibility is maintained as mentioned in the commit
message.

-- 
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

  parent reply	other threads:[~2015-12-16 10:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1445422216-29375-1-git-send-email-sudeep.holla@arm.com>
     [not found] ` <1445422216-29375-1-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2015-10-21 10:10   ` [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source Sudeep Holla
2015-12-15 16:35     ` Sudeep Holla
     [not found]       ` <56704141.8070308-5wv7dgnIgG8@public.gmane.org>
2015-12-15 23:32         ` Krzysztof Kozlowski
     [not found]           ` <5670A2F2.5060009-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-12-16 10:32             ` Sudeep Holla [this message]
2015-12-16 23:38               ` Krzysztof Kozlowski
2015-12-16 23:49     ` Krzysztof Kozlowski
2016-01-28  8:11       ` Krzysztof Kozlowski
     [not found]         ` <56A9CD1A.8010800-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-01-28 15:59           ` [UPDATE] " Sudeep Holla
2016-01-29  0:11             ` Krzysztof Kozlowski
2015-10-21 10:10 ` [PATCH 16/19] ARM: dts: s5pv210: " Sudeep Holla
2015-12-15 16:37   ` Sudeep Holla
2015-12-16 23:52   ` Krzysztof Kozlowski

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=56713DD8.1050001@arm.com \
    --to=sudeep.holla-5wv7dgnigg8@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@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