Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932769AbbFRRyL (ORCPT ); Thu, 18 Jun 2015 13:54:11 -0400 Received: from mailout3.samsung.com ([203.254.224.33]:41287 "EHLO mailout3.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932754AbbFRRyB (ORCPT ); Thu, 18 Jun 2015 13:54:01 -0400 X-AuditID: cbfee61b-f79416d0000014c0-2a-558305b78631 From: Bartlomiej Zolnierkiewicz To: Mike Turquette Cc: Kukjin Kim , Viresh Kumar , Lukasz Majewski , Kukjin Kim , Heiko Stuebner , Kevin Hilman , linux-pm@vger.kernel.org, Tomasz Figa , linux-kernel@vger.kernel.org, Chanwoo Choi , Thomas Abraham , linux-arm-kernel@lists.infradead.org, Sylwester Nawrocki , Javier Martinez Canillas , linux-samsung-soc@vger.kernel.org Subject: Re: [PATCH 0/6] cpufreq: use generic cpufreq drivers forExynos4210platform Date: Thu, 18 Jun 2015 19:53:14 +0200 Message-id: <1705390.i4bNz9zR7Y@amdc1976> User-Agent: KMail/4.13.3 (Linux/3.13.0-53-generic; KDE/4.13.3; x86_64; ; ) In-reply-to: <556F8C1D.9050906@kernel.org> References: <'@samsung.com> <55549E03.6040105@kernel.org> <556F8C1D.9050906@kernel.org> MIME-version: 1.0 Content-transfer-encoding: 7Bit Content-type: text/plain; charset=us-ascii X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsVy+t9jAd3trM2hBvs+8Fhc//Kc1eL/o9es Fkd/F1j0LrjKZtH/+DWzxdfDKxgt3jzczGix6fE1VovLu+awWXzuPcJoMeP8PiaLpxMuslkc ftPOatGxjNFi1a4/jBYbv3o4CHj8fX6dxWPnrLvsHptWdbJ53Lm2h81j85J6j74tqxg9tl+b x+zxeZNcAEcUl01Kak5mWWqRvl0CV8aaq4dYCnaJVGw9fpe1gbFZoIuRk0NCwESi/dp9dghb TOLCvfVsXYxcHEICixgltra3sUM4XxklWtedZQWpYhOwkpjYvooRxBYR0JLYdqAVrINZ4CSL xN7WVWBFwgKhEiv+HGUBsVkEVCXWtd0CW8EroCnRsWQNmC0q4CXR+3MdUDMHByfQoOP3Y0HC QgKRErcvL2WGKBeU+DH5HtgYZgF5iX37p7JC2FoS63ceZ5rAKDALSdksJGWzkJQtYGRexSia WpBcUJyUnmukV5yYW1yal66XnJ+7iREcV8+kdzCuarA4xCjAwajEwxvxtilUiDWxrLgy9xCj BAezkgiv52egEG9KYmVValF+fFFpTmrxIUZpDhYlcd6T+T6hQgLpiSWp2ampBalFMFkmDk6p BsaVf+6evxzP/ina7fj1Dv6n3utM9r6Y8vmbYc7NTc8n/O4SjUub4fw+tll/McOMhvrKONM5 Ehs4+jdwiNx0v5d9vqMgRuWRbJ+L/mnhSJ7ONoOH99TEtokJZgjvrbTwPn3U86EPG+P/6Sav NzLN//jiz8kGG9UNExeKbqi/+fWX058vkqn1jf+VWIozEg21mIuKEwFmUzCppwIAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2794 Lines: 76 Hi, Mike, could you please take a look at patches #1 and #2 (#1 is a 4 line change to a Common Clock Framework and #2 is ARM Exynos specific)? This series has been waiting on your feedback since 3rd of April. :( Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics On Thursday, June 04, 2015 08:22:05 AM Kukjin Kim wrote: > On 05/14/15 22:07, Kukjin Kim wrote: > > On 05/14/15 14:10, Viresh Kumar wrote: > >> On 14-05-15, 13:07, Kukjin Kim wrote: > >>> On 05/13/15 23:08, Bartlomiej Zolnierkiewicz wrote: > >>>> > >>>> Hi, > >>>> > >>> Hi Bart, > >>> > >>>> On Friday, April 03, 2015 06:43:43 PM Bartlomiej Zolnierkiewicz wrote: > >>>>> Hi, > >>>>> > >>>>> This patch series removes the use of Exynos4210 specific support > >>>>> from cpufreq-exynos driver and enables the use of cpufreq-dt driver > >>>>> for this platform. > >>>> > >>>> Gentle Ping. Mike/Kukjin/Viresh could you please review/ack relevant > >>>> patches (patches #1-3 are for clock subsystem, patches #4-5 for Exynos > >>>> mach/dts and patch #6 is for cpufreq subsystem)? > >> > >> Sorry I thought I already Acked an older version of this set and so > >> didn't went for it again. Done now. > >> > >>> Yes, I totally agreed with this patches for arch side changes and this > >>> approach when Thomas posted. > >>> > >>>> Also what is your > >>>> preferred way to upstream them (patches are not independent so it would > >>>> be best to merge them through one tree, otherwise synchronization of > >>>> git pulls between different subsystem trees will be needed)? > >>>> > >>> I can provide topic branch for arch side changes even it is small. I > >>> think once Viresh and Mike make each topic branch based on -rc or the > >>> smallest changes from each subsystem then I could handle this series or > >>> Viresh or Mike need to handle this series with merging each topic > >>> branches in subsystem. I'm fine either way. > >>> > >>> Viresh and Mike, how do you think about that? > >> > >> For cpufreq subsystem changes, you can take them in your tree. > >> > > Hi Viresh, OK, I will take the cpufreq changes with your ack. Thanks for > > your confirmation. > > > > Hi Mike and Sylwester, > > How can we handle this series well without any problems? hmm... > > > Still I need to get clock guys' ack or any comments on this series... > > - Kukjin > > >>>> I'm still hoping that this patchset will make it into v4.2 as there are > >>>> no known issues with it (except minor coding nit for patch #5)... > >>>> > >>> Sure, why not :-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/