From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933275AbbENKyA (ORCPT ); Thu, 14 May 2015 06:54:00 -0400 Received: from mailout4.samsung.com ([203.254.224.34]:59668 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932299AbbENKx4 (ORCPT ); Thu, 14 May 2015 06:53:56 -0400 X-AuditID: cbfee61b-f79536d000000f1f-d9-55547ec13654 From: Bartlomiej Zolnierkiewicz To: Viresh Kumar Cc: Kukjin Kim , Thomas Abraham , Sylwester Nawrocki , Mike Turquette , Kukjin Kim , Tomasz Figa , Lukasz Majewski , Heiko Stuebner , Chanwoo Choi , Kevin Hilman , Javier Martinez Canillas , linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/6] cpufreq: use generic cpufreq drivers for Exynos4210platform Date: Thu, 14 May 2015 12:53:14 +0200 Message-id: <3051718.I09JWVi0Gb@amdc1976> User-Agent: KMail/4.13.3 (Linux/3.13.0-51-generic; KDE/4.13.3; x86_64; ; ) In-reply-to: <20150514051046.GB9887@linux> References: <'@samsung.com> <55541F92.4020404@kernel.org> <20150514051046.GB9887@linux> MIME-version: 1.0 Content-transfer-encoding: 7Bit Content-type: text/plain; charset=us-ascii X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsVy+t9jQd2DdSGhBr//y1hc//Kc1eL/o9es Fkd/F1j0LrjKZtH/+DWzxdfDKxgt3jzczGix6fE1VovLu+awWXzuPcJoMeP8PiaLpxMuslkc ftPOatGxjNFi1a4/jBYbv3o4CHj8fX6dxWPnrLvsHptWdbJ53Lm2h81j85J6j74tqxg9tl+b x+zxeZNcAEcUl01Kak5mWWqRvl0CV8bSU59ZCu4KVRx5/YelgXEnXxcjB4eEgInE3Tv2XYyc QKaYxIV769m6GLk4hASmM0pcPbCQBcL5yihxrfk3E0gVm4CVxMT2VYwgzSICWhIvb6aC1DAL nGSR6Lrynh2kRlggTOLRmSWMIDaLgKrEp22vwXp5BTQlJm8/wgxiiwp4SRyasoEVxOYEmrPr zhuwGiGBSImnk/6zQNQLSvyYfA/MZhaQl9i3fyorhK0lsX7ncaYJjAKzkJTNQlI2C0nZAkbm VYyiqQXJBcVJ6blGesWJucWleel6yfm5mxjBUfVMegfjqgaLQ4wCHIxKPLwvHEJChVgTy4or cw8xSnAwK4nwro8GCvGmJFZWpRblxxeV5qQWH2KU5mBREuc9me8TKiSQnliSmp2aWpBaBJNl 4uCUamCM1ki5WWPO5vnJ/pB/xOHrFw8qSAkYvK1kTYqZ+kljyYyYMOuTC2oi+2we3/3weH2N UuxKu5sXeQ+6lzTsfW02jWn5Ne9fAo+c3939nbHMXvb/DFbDV6ffzlB9XKu/df6xrXk3zvHO TA4+0x+254vQK9U7Py/G/z3WEfj+U8+zf8sU7ubOP66zVImlOCPRUIu5qDgRAEb8so6mAgAA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, May 14, 2015 10:40:46 AM 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. Thanks! > > 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. > > > > 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 :-) > > One thing that looked wrong to me is the email id of Thomas.. > I believe he has already left Samsung and his id wouldn't exist > anymore. Right ? This doesn't seem to be a case. His email doesn't bounce and his id exists (I've just checked this). I think that he is just very busy with some other work. > Then I wouldn't recommend something that doesn't exist to get merged > now. Probably use another email id of his. Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics From mboxrd@z Thu Jan 1 00:00:00 1970 From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz) Date: Thu, 14 May 2015 12:53:14 +0200 Subject: [PATCH 0/6] cpufreq: use generic cpufreq drivers for Exynos4210platform In-Reply-To: <20150514051046.GB9887@linux> References: <'@samsung.com> <55541F92.4020404@kernel.org> <20150514051046.GB9887@linux> Message-ID: <3051718.I09JWVi0Gb@amdc1976> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thursday, May 14, 2015 10:40:46 AM 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. Thanks! > > 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. > > > > 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 :-) > > One thing that looked wrong to me is the email id of Thomas.. > I believe he has already left Samsung and his id wouldn't exist > anymore. Right ? This doesn't seem to be a case. His email doesn't bounce and his id exists (I've just checked this). I think that he is just very busy with some other work. > Then I wouldn't recommend something that doesn't exist to get merged > now. Probably use another email id of his. Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics