From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=DelH=WE=vger.kernel.org=linux-clk-owner@kernel.org>
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 B4CB4C0650F
	for <linux-clk@archiver.kernel.org>; Thu,  8 Aug 2019 15:00:35 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 84B2121874
	for <linux-clk@archiver.kernel.org>; Thu,  8 Aug 2019 15:00:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1565276435;
	bh=7ABlbrr024uC6TeWzpfCfq9aUOmdkt772JW/xbpxA4Q=;
	h=In-Reply-To:References:Subject:From:Cc:To:Date:List-ID:From;
	b=Q7RY9aPvp7wLnO0zOjiYhWEwzM1B1Q+IwoOpvq2WTJ4ipEt1Cpei+xycRwJRJxEH/
	 s30qUJXtZbOtRJ85WBRFdFgSrTrkpXa7TxzXioFbS7saCOjpkCd/kmOqImZJ8vIhni
	 r6YRdbhCylSr7CLe40pCGlFAYqVwcENORy5Lymhg=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1729925AbfHHPAf (ORCPT <rfc822;linux-clk@archiver.kernel.org>);
        Thu, 8 Aug 2019 11:00:35 -0400
Received: from mail.kernel.org ([198.145.29.99]:41188 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1728380AbfHHPAf (ORCPT <rfc822;linux-clk@vger.kernel.org>);
        Thu, 8 Aug 2019 11:00:35 -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 6A890217D7;
        Thu,  8 Aug 2019 15:00:34 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1565276434;
        bh=7ABlbrr024uC6TeWzpfCfq9aUOmdkt772JW/xbpxA4Q=;
        h=In-Reply-To:References:Subject:From:Cc:To:Date:From;
        b=ITO6wphfn03+Nq0nJtFCyJCa9O06MVYjKZw3c6HlAztuSUSoDy/kzaxCRTZf4rbdT
         COJeEwFzkStAiTJtpokkS6AwEK4fwrvx4ebMzVcUyMLvzwCTbjdlF9i8FplNOnjAse
         eOaoygo89uORFI/foWt3HdnqkatV30mLu/7pFgIQ=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <29453ee8e820457d87a8faf9d496390e59c6826f.1562073871.git.leonard.crestez@nxp.com>
References: <68e96af2df96512300604d797ade2088d7e6e496.1562073871.git.leonard.crestez@nxp.com> <29453ee8e820457d87a8faf9d496390e59c6826f.1562073871.git.leonard.crestez@nxp.com>
Subject: Re: [PATCH v3 2/2] clk: Assert prepare_lock in clk_core_get_boundaries
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     Michael Turquette <mturquette@baylibre.com>,
        linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
To:     Geert Uytterhoeven <geert@linux-m68k.org>,
        Leonard Crestez <leonard.crestez@nxp.com>
User-Agent: alot/0.8.1
Date:   Thu, 08 Aug 2019 08:00:33 -0700
Message-Id: <20190808150034.6A890217D7@mail.kernel.org>
Sender: linux-clk-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-clk.vger.kernel.org>
X-Mailing-List: linux-clk@vger.kernel.org

Quoting Leonard Crestez (2019-07-02 06:27:10)
> This function iterates the clk consumer list on clk_core so it must be
> called under prepare_lock. This is already done by all callers but add a
> lockdep assert to check anyway.
>=20
> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>=20
> ---

Applied to clk-next