From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: Keerthy <a0393675@ti.com>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
Lokesh Vutla <lokeshvutla@ti.com>, Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
galak@codeaurora.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: dts: dra7: Correct clock tree for sys_32k_ck
Date: Fri, 1 Apr 2016 12:06:27 -0700 [thread overview]
Message-ID: <20160401190627.GO9329@atomide.com> (raw)
In-Reply-To: <56FEC297.50102@ti.com>
* Tero Kristo <t-kristo@ti.com> [160401 11:50]:
>
> Looks like a merge conflict to me, sys_32k_ck has gone under clockdomains
> for some reason. It should be under clocks.
Oh OK, I'll wait for an updated patch against v4.6-rc1 then.
Might be worth checking it applies cleanly against
omap-for-v4.6/fixes-rc1 too.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org>
Cc: Keerthy <a0393675-l0cyMroinI0@public.gmane.org>,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Lokesh Vutla <lokeshvutla-l0cyMroinI0@public.gmane.org>,
Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2] ARM: dts: dra7: Correct clock tree for sys_32k_ck
Date: Fri, 1 Apr 2016 12:06:27 -0700 [thread overview]
Message-ID: <20160401190627.GO9329@atomide.com> (raw)
In-Reply-To: <56FEC297.50102-l0cyMroinI0@public.gmane.org>
* Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org> [160401 11:50]:
>
> Looks like a merge conflict to me, sys_32k_ck has gone under clockdomains
> for some reason. It should be under clocks.
Oh OK, I'll wait for an updated patch against v4.6-rc1 then.
Might be worth checking it applies cleanly against
omap-for-v4.6/fixes-rc1 too.
Regards,
Tony
--
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
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: dra7: Correct clock tree for sys_32k_ck
Date: Fri, 1 Apr 2016 12:06:27 -0700 [thread overview]
Message-ID: <20160401190627.GO9329@atomide.com> (raw)
In-Reply-To: <56FEC297.50102@ti.com>
* Tero Kristo <t-kristo@ti.com> [160401 11:50]:
>
> Looks like a merge conflict to me, sys_32k_ck has gone under clockdomains
> for some reason. It should be under clocks.
Oh OK, I'll wait for an updated patch against v4.6-rc1 then.
Might be worth checking it applies cleanly against
omap-for-v4.6/fixes-rc1 too.
Regards,
Tony
next prev parent reply other threads:[~2016-04-01 19:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 12:03 [PATCH v2] ARM: dts: dra7: Correct clock tree for sys_32k_ck Keerthy
2016-03-14 12:03 ` Keerthy
2016-03-14 12:03 ` Keerthy
2016-03-30 21:18 ` Tony Lindgren
2016-03-30 21:18 ` Tony Lindgren
2016-03-30 21:18 ` Tony Lindgren
2016-03-30 21:32 ` Tony Lindgren
2016-03-30 21:32 ` Tony Lindgren
2016-03-30 21:32 ` Tony Lindgren
2016-03-31 6:30 ` Tero Kristo
2016-03-31 6:30 ` Tero Kristo
2016-03-31 6:30 ` Tero Kristo
2016-03-31 9:22 ` Keerthy
2016-03-31 9:22 ` Keerthy
2016-03-31 9:22 ` Keerthy
2016-03-31 17:00 ` Tony Lindgren
2016-03-31 17:00 ` Tony Lindgren
2016-03-31 17:00 ` Tony Lindgren
2016-04-01 15:36 ` Tony Lindgren
2016-04-01 15:36 ` Tony Lindgren
2016-04-01 15:36 ` Tony Lindgren
2016-04-01 18:48 ` Tero Kristo
2016-04-01 18:48 ` Tero Kristo
2016-04-01 18:48 ` Tero Kristo
2016-04-01 19:06 ` Tony Lindgren [this message]
2016-04-01 19:06 ` Tony Lindgren
2016-04-01 19:06 ` Tony Lindgren
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=20160401190627.GO9329@atomide.com \
--to=tony@atomide.com \
--cc=a0393675@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.