From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6B68FC433EF for ; Wed, 1 Jun 2022 11:06:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1352482AbiFALGd (ORCPT ); Wed, 1 Jun 2022 07:06:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54862 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344751AbiFALG0 (ORCPT ); Wed, 1 Jun 2022 07:06:26 -0400 Received: from mx-out1.startmail.com (mx-out1.startmail.com [145.131.90.139]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D253C880FE; Wed, 1 Jun 2022 04:06:24 -0700 (PDT) Date: Wed, 1 Jun 2022 06:06:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=startmail.com; s=2020-07; t=1654081583; bh=AP3oFJBNtpyqWEDwPuJs+2d2Hm8MZqU21we76PtPVCU=; h=Date:From:To:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To:From:Subject:To:Date: Sender:Content-Type:Content-Transfer-Encoding:Content-Disposition: Mime-Version:Reply-To:In-Reply-To:References:Message-Id:Autocrypt; b=V13YoxjYEIOd1Iag5EpQsjGEP++IfmJGqBwINVQ965F/Fb5P/TD0qM50U7+3XhOap zf//6f3ifo7ursws8QVdcy1TWCkq3ObGanOaEZAGk9ogIbjzYiOQxYqkgNRy75hfF2 AQEu91CC0XEbRfTrIUIyEqwwiM84v9Sngb7oYaXRgaUizAvdtWL3M4aI5AKHkGBL1g yt+s9HdSkPcScDZjqlFpt/bF+EmlAMXvMtXuFzoWwWAH+8urkyMDjfHjCfQqwL4NZ0 BbqRt959GznLMf7YJND8IoZoHwJdIc7pypzcbZk5QIOt9kvGdiWiGG23VAsMnIdzD3 PZVdTW/SOu27g== From: "Marty E. Plummer" To: Krzysztof Kozlowski Cc: arnd@arndb.de, cai.huoqing@linux.dev, christian.koenig@amd.com, devicetree@vger.kernel.org, gengdongjiu@huawei.com, krzysztof.kozlowski+dt@linaro.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, linux@armlinux.org.uk, michael@walle.cc, miquel.raynal@bootlin.com, mturquette@baylibre.com, novikov@ispras.ru, olof@lixom.net, p.yadav@ti.com, rdunlap@infradead.org, richard@nod.at, robh+dt@kernel.org, sboyd@kernel.org, soc@kernel.org, sumit.semwal@linaro.org, tudor.ambarus@microchip.com, vigneshr@ti.com, xuwei5@hisilicon.com Subject: Re: [RFC v2 1/2] clk: hisilicon: add CRG driver Hi3521a SoC Message-ID: <20220601110616.xmxih663kxgupszv@proprietary-killer> References: <20220501054440.2434247-1-hanetzer@startmail.com> <20220501173423.2473093-1-hanetzer@startmail.com> <20220501173423.2473093-2-hanetzer@startmail.com> <20220601105846.7hriawg3stxb657f@proprietary-killer> <630b0d13-6778-2508-6a34-9daa0358047d@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <630b0d13-6778-2508-6a34-9daa0358047d@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 01, 2022 at 01:00:38PM +0200, Krzysztof Kozlowski wrote: > On 01/06/2022 12:58, Marty E. Plummer wrote: > > On Tue, May 03, 2022 at 01:37:42PM +0200, Krzysztof Kozlowski wrote: > >> On 01/05/2022 19:34, Marty E. Plummer wrote: > >>> Add CRG driver for Hi3521A SoC. CRG (Clock and Reset Generator) module > >>> generates clock and reset signals used by other module blocks on SoC. > >>> > >>> Signed-off-by: Marty E. Plummer > >>> --- > >>> drivers/clk/hisilicon/Kconfig | 8 ++ > >>> drivers/clk/hisilicon/Makefile | 1 + > >>> drivers/clk/hisilicon/crg-hi3521a.c | 141 ++++++++++++++++++++++ > >>> include/dt-bindings/clock/hi3521a-clock.h | 34 ++++++ > >> > >> Bindings go to separate patch. Your patchset is unmerge'able. > >> > > So, assuming I have the following patches: > > 1: +include/dt-bindings/clock/hi3521a-clock.h > > 2: +drivers/clk/hisilicon/crg-hi3521a.c > > 3: +Documentation/devicetree/bindings/whatever > > > > In what order should they be applied? > > Applied or sent? The maintainer will apply them in proper order, this is > bisectable. > > Either or. Whatever makes the workload easier is what I'm looking for. > Best regards, > Krzysztof