Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933300AbbHZCRI (ORCPT ); Tue, 25 Aug 2015 22:17:08 -0400 Received: from mail-pa0-f41.google.com ([209.85.220.41]:33480 "EHLO mail-pa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933179AbbHZCRE (ORCPT ); Tue, 25 Aug 2015 22:17:04 -0400 Date: Wed, 26 Aug 2015 07:46:59 +0530 From: Viresh Kumar To: Pi-Cheng Chen Cc: "Rafael J. Wysocki" , Matthias Brugger , Mark Rutland , Michael Turquette , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Linux Kernel Mailing List , "linux-pm@vger.kernel.org" , Linaro Kernel Mailman List , linux-mediatek@lists.infradead.org Subject: Re: [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver Message-ID: <20150826021659.GD8784@linux> References: <1439803465-19683-1-git-send-email-pi-cheng.chen@linaro.org> <1617873.VRHfat3V76@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 838 Lines: 19 On 26-08-15, 09:25, Pi-Cheng Chen wrote: > The [3/3] is based on Mediatek SoC maintainer tree[1] and the patch which > introduce a new clock type[2] consumed by MT8173 cpufreq driver. So it will > cause some conflicts if it goes through your tree. I am not sure how this > should be handled, but should it be merged through Mediatek SoC maintainer > tree? Just get that applied to MTK tree, it doesn't have any dependency on rest of the patches for build/boot. The only thing is that cpufreq wouldn't work and it will work as soon as Rafael's and MTK's trees are merged by Linus. -- viresh -- 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/