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 X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A4732C433E1 for ; Thu, 25 Jun 2020 00:42:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6F2DD2078D for ; Thu, 25 Jun 2020 00:42:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593045764; bh=dR9E4HhUJ5qnG0JO1ZiYFIT9TNxSCP6TdmL1mbcb1qk=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=T5pB4kYxxqxiDO0vWhFUGX7QNc+uTlebZuUWUX0JNsiCI+ZARoN7xCjipARqmbkv8 LqyGsjf0p43gDOt5RxcFEIHYdb5Et35mtwHvmHkOif9d9Mfn1NO++MYsvhbXsDZ/lY M4G1wGElECXjNqaeWJDZPy4jNdaAOJ+/mWQqLb58= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389095AbgFYAmn (ORCPT ); Wed, 24 Jun 2020 20:42:43 -0400 Received: from mail.kernel.org ([198.145.29.99]:56934 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389054AbgFYAmk (ORCPT ); Wed, 24 Jun 2020 20:42:40 -0400 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9649F2078D; Thu, 25 Jun 2020 00:42:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593045759; bh=dR9E4HhUJ5qnG0JO1ZiYFIT9TNxSCP6TdmL1mbcb1qk=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=DhR47hUtA67b17haoDR4pzfB8yZ0xJNni+0r2H3JoiMsLV8IWDGZN+q+movkC9xKB Cl95DyvpX9xVmNjU0sqkP7tElV5qayA27IpUjb7cIjogAWCa6cLmvOhWhA0Crbdejv KSeA7dDl5+1R1e5HpGqx4a3CA6p86kAL6rstg2Fg= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <0342572daa561dc1bb4c9fd10641b2016493e32b.1592210452.git-series.maxime@cerno.tech> References: <0342572daa561dc1bb4c9fd10641b2016493e32b.1592210452.git-series.maxime@cerno.tech> Subject: Re: [PATCH v5 05/27] clk: bcm: rpi: Statically init clk_init_data From: Stephen Boyd Cc: linux-rpi-kernel@lists.infradead.org, bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Dave Stevenson , Tim Gover , Phil Elwell , Mike Turquette , linux-clk@vger.kernel.org, Philipp Zabel , Maxime Ripard To: Maxime Ripard , Nicolas Saenz Julienne Date: Wed, 24 Jun 2020 17:42:38 -0700 Message-ID: <159304575897.62212.17561160982634673134@swboyd.mtv.corp.google.com> User-Agent: alot/0.9 Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Maxime Ripard (2020-06-15 01:40:45) > Instead of declaring the clk_init_data and then calling memset on it, just > initialise properly. >=20 > Cc: Michael Turquette > Cc: Stephen Boyd > Cc: linux-clk@vger.kernel.org > Acked-by: Nicolas Saenz Julienne > Reviewed-by: Stephen Boyd > Tested-by: Nicolas Saenz Julienne > Signed-off-by: Maxime Ripard > --- Applied to clk-next