From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Brugger Subject: Re: [PATCH v4 00/12] Mediatek MT8183 clock and scpsys support Date: Thu, 21 Feb 2019 09:36:24 +0100 Message-ID: References: <20190201083016.25856-1-weiyi.lu@mediatek.com> <20190201083016.25856-2-weiyi.lu@mediatek.com> <155069033021.77512.14493210110678229730@swboyd.mtv.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <155069033021.77512.14493210110678229730@swboyd.mtv.corp.google.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Stephen Boyd , Nicolas Boichat , Rob Herring , Stephen Boyd , Weiyi Lu Cc: James Liao , Fan Chen , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org, srv_heupstream@mediatek.com, stable@vger.kernel.org List-Id: linux-mediatek@lists.infradead.org On 20/02/2019 20:18, Stephen Boyd wrote: > Quoting Weiyi Lu (2019-02-01 00:30:04) >> This series is based on v5.0-rc1 and most of changes are extracted from series below >> (clock/scpsys common changes for both MT8183 & MT6765) >> https://patchwork.kernel.org/patch/10528495/ >> (clock support of MT8183) >> https://patchwork.kernel.org/patch/10549891/ >> >> The whole series is composed of >> clock common changes for both MT8183 & MT6765 (PATCH 1-3), >> scpsys common changes for both MT8183 & MT6765 (PATCH 4), >> clock support of MT8183 (PATCH 5-8), >> scpsys support of MT8183 (PATCH 9-11) and >> resend a clock patch long time ago(PTACH 12). > > What's the merge plan here? Do you want me to apply these patches to clk > tree? Will someone be sending me a pull request for mediatek clk changes > this cycle? It's getting pretty late for much of anything making this > upcoming merge window. > As far as I can see, the clock patches are independent, so I think it is OK to take them. SCPSYS patches will go through my tree once they are in shape. Do you prefer to get pull requests for clock patches? I wasn't aware of that. But if you prefer that, we can find someone who prepares every merge window a pull request. Regards, Matthias