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 C4D61C7618D for ; Wed, 15 Mar 2023 19:05:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232535AbjCOTFE (ORCPT ); Wed, 15 Mar 2023 15:05:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42702 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232500AbjCOTEv (ORCPT ); Wed, 15 Mar 2023 15:04:51 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DF6CB6C19B; Wed, 15 Mar 2023 12:04:49 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 700D561E07; Wed, 15 Mar 2023 19:04:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CAF1EC433D2; Wed, 15 Mar 2023 19:04:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1678907088; bh=PHCqtfNPtykLQzgOmD479r+vtvy5dP8Tx6mGL6Sg3ak=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=qKdBV3PNcXnrOccuRb2+b9kinnFWwz05lqXdy54fU9J37SpHDUIgXnn+I5S/6WeHL SK5wZW1D/TPAQUvevh/VOdHiBJ36RAZHiRiiCAQMG2i2mVflMV8GVgPn+bb64VQ1r7 FTmMRDRRa7LtxOdgTvCoT5RYJ73jU61FiUUwua4PCTNb26Ru8s2IGnKwIAVeG/uWrD hXcWvJuaDN5zf8fsF5/oxF85WKAfK8HHP0LGVdxLOLX3zQOSxLkpsf5iureCBqXgGi vlZxwRkaz+ZrHr3/mxSHeqj3leMNtVB54aDyYPuSGMUH/4A0f70QY4VEzOKuFgO3g/ y5kek1OV90Atg== Message-ID: <48d30bc1f094bee18a2180a5b8e65e40.sboyd@kernel.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20230210111141.1379645-1-keguang.zhang@gmail.com> <20230315092910.GA8008@alpha.franken.de> Subject: Re: [PATCH] MIPS: loongson32: Update the clock initialization From: Stephen Boyd Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org, Serge Semin To: Keguang Zhang , Thomas Bogendoerfer Date: Wed, 15 Mar 2023 12:04:46 -0700 User-Agent: alot/0.10 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Keguang Zhang (2023-03-15 02:43:02) > On Wed, Mar 15, 2023 at 5:29=E2=80=AFPM Thomas Bogendoerfer > wrote: > > > > On Wed, Mar 15, 2023 at 11:07:23AM +0800, Keguang Zhang wrote: > > > On Sat, Feb 11, 2023 at 7:31=E2=80=AFAM Stephen Boyd wrote: > > > > > > > > Quoting Keguang Zhang (2023-02-10 03:11:41) > > > > > The Loongson-1 clock driver is under re-implementation > > > > > to add DT support. As a result, ls1x_clk_init() will be dropped s= oon. > > > > > Therefore, call of_clk_init() for clock initialization instead. > > > > > > > > > > Link: https://lore.kernel.org/all/20230209132614.1079198-3-keguan= g.zhang@gmail.com > > > > > Link: https://lore.kernel.org/all/20230209132614.1079198-4-keguan= g.zhang@gmail.com > > > > > > Hi Thomas, > > > Sorry to bother you. > > > For fear of raising build error, is it possible to merge this patch > > > before the above two patches getting applied? > > > Or is there anything to improve? > > > Thanks very much! > > > > the IMHO best way would be to let this patch go the same way as > > the other patch set. So Stephen could you take this into your > > tree, too ? > > > Sure. Will do. >=20 Please resend this patch along with the loongson patches that it goes with.