From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Pawe=c5=82_Jarosz?= Subject: Re: [PATCH v2 0/2] Assign RK3066 clocks at boot time Date: Fri, 14 Oct 2016 16:11:26 +0200 Message-ID: <58a16125-d0bd-1019-eee3-615b35c71c6a@gmail.com> References: <1569308.lsrqUgJ5m1@phil> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1569308.lsrqUgJ5m1@phil> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+glpar-linux-rockchip=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Heiko Stuebner Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org, mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org, sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org, linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-rockchip.vger.kernel.org W dniu 14.10.2016 o 15:28, Heiko Stuebner pisze: > changes look good. One thing to keep in mind is that we need clock-id > additions in a separate patch (as they need to be on a shared branch). > > I can do this split of patch1 on my own here, so no need to resend the series > and will do that after 4.9-rc1 (probably somewhere after sunday) as I need a > stable base for that shared branch. > > > Heiko Thanks Heiko. From mboxrd@z Thu Jan 1 00:00:00 1970 From: paweljarosz3691@gmail.com (=?UTF-8?Q?Pawe=c5=82_Jarosz?=) Date: Fri, 14 Oct 2016 16:11:26 +0200 Subject: [PATCH v2 0/2] Assign RK3066 clocks at boot time In-Reply-To: <1569308.lsrqUgJ5m1@phil> References: <1569308.lsrqUgJ5m1@phil> Message-ID: <58a16125-d0bd-1019-eee3-615b35c71c6a@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org W dniu 14.10.2016 o 15:28, Heiko Stuebner pisze: > changes look good. One thing to keep in mind is that we need clock-id > additions in a separate patch (as they need to be on a shared branch). > > I can do this split of patch1 on my own here, so no need to resend the series > and will do that after 4.9-rc1 (probably somewhere after sunday) as I need a > stable base for that shared branch. > > > Heiko Thanks Heiko.