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 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 153FFC3A59C for ; Fri, 16 Aug 2019 14:51:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DA20C2171F for ; Fri, 16 Aug 2019 14:51:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565967096; bh=zOrA4mX823PTQ9324s7EdYM6BIvZpPyOoitLCrgVvk0=; h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From; b=YpYRz9NtFPIAGqethKiS7lf6cgtXdOk9EeNObb16pX4RF823ilUrx2qQaVdjPugmO lFDLQviRr5QIi5cWIZfOAS0jW1lq8OHLaQkNuO6z+KNdTdpdR7afBwTAPEA1KRuSs5 s+hrqOzdMXQzx9txyAu1eMZPLv0RKJ6vNB6iOyaI= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727405AbfHPOvg (ORCPT ); Fri, 16 Aug 2019 10:51:36 -0400 Received: from mail.kernel.org ([198.145.29.99]:55532 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726032AbfHPOvg (ORCPT ); Fri, 16 Aug 2019 10:51:36 -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 82244206C1; Fri, 16 Aug 2019 14:51:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565967095; bh=zOrA4mX823PTQ9324s7EdYM6BIvZpPyOoitLCrgVvk0=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=LL8usYxiwzoUv0BUg4MLQ5VUHksimEhTqqviAtiNur5nqY93dKkViHkIW5eonkdhv KtYz1pqkyQsMz9iTlHAv2DEeeylH/u/ehEoiLFo501CeNJ9vlJ6f69fJM3nx0Zx5Il ynPAYPU7hD24E6J7c9yUJYaniY6OyUwdizYs5unY= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20190815221249.53235-1-sboyd@kernel.org> References: <20190815221249.53235-1-sboyd@kernel.org> Subject: Re: [PATCH] clk: ti: Don't reference clk_init_data after registration From: Stephen Boyd Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-omap@vger.kernel.org, Tero Kristo , Tony Lindgren To: Michael Turquette , Stephen Boyd User-Agent: alot/0.8.1 Date: Fri, 16 Aug 2019 07:51:34 -0700 Message-Id: <20190816145135.82244206C1@mail.kernel.org> Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Stephen Boyd (2019-08-15 15:12:49) > A future patch is going to change semantics of clk_register() so that > clk_hw::init is guaranteed to be NULL after a clk is registered. Avoid > referencing this member here so that we don't run into NULL pointer > exceptions. >=20 > Cc: Tero Kristo > Cc: Tony Lindgren > Signed-off-by: Stephen Boyd > --- >=20 > This might be causing boot regressions in linux-next. Not sure. >=20 I don't see linux-next boot regressions in kernel-ci so it must be working.