Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp415732ybm;
        Tue, 26 May 2020 21:31:24 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJyLkBemYey49fBGHvq/LJIoG7PdwA7qdsc546EdkmSKvZywEAzY5SbfT2gDx2AEy5ntS8ua
X-Received: by 2002:a05:600c:24d1:: with SMTP id 17mr2262087wmu.48.1590553884074;
        Tue, 26 May 2020 21:31:24 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1590553884; cv=none;
        d=google.com; s=arc-20160816;
        b=usu+gJaT0rlAuJ2j3Flu3DGfWkw7cNo2NxMcIoTH/y57nnjC5o+fkh5HzdursBY4xh
         NDTv2VAUbXS7AINP4zAcdTXfMRJLkTI9yz4xB89ahgWE9UbrkCqUVifUPsuurGtguSg0
         mSLMj56pREi45oARfwP+NQs6T30OIhcNprSDifdxDJD6VhyBRHkwI9t8zyBrbWcNO/qT
         m9unZfteV5ap2g4kpjGUa0Ety8PVT6jl4MMyYV1nkD2vZbj8PW4aUES0azfg7YwK6TF+
         GyJixgKzU9WbFOLWiWb8Bz29B9z0CxUCUP1RKGyQ4K3gTn/hmoIQaZuRnO/gzVoafD3E
         pLQA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:user-agent:message-id:date:to:cc:from
         :subject:references:in-reply-to:content-transfer-encoding
         :mime-version:dkim-signature;
        bh=JrTsD2iMGSvX30rQ6pUzDT7ruFhGoJkwwO5nT3DHnLA=;
        b=K1WZjvvjY1orraMrExsa2/oOURbkIOELDeesmL7zFoJ0VM5bcuondfcGCUttiPAzVb
         WWsBLFpg5k+T82oULHzS3sz7TG+G9Py/5+j+qAwmJ31d65PhAsA5QCNXTgrj++WaRRa8
         At6IoJp2/8tEgLkgvJ4uF0WrYbH2Xybl5KaaJOJv+QhTLlmtiMqdDgsq9zqZRtB3LMyE
         jpqcAIJPvDwth4x7J6w7w06Y5phJq+BFHD8wnszD+k+e7jwt8V06S5Hwd0CAVtVjHTG2
         gRzvlS/LIAIsnyhhpaWMLXqqcUbY6bwnAOcayqlrnGj97DqSr3pP3mod55gHGbjdKzQv
         /9Ng==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@kernel.org header.s=default header.b=Xh1Jo2Y4;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18])
        by mx.google.com with ESMTP id i12si1225162ejc.462.2020.05.26.21.31.00;
        Tue, 26 May 2020 21:31:24 -0700 (PDT)
Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@kernel.org header.s=default header.b=Xh1Jo2Y4;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1727983AbgE0BB3 (ORCPT <rfc822;epopevad@gmail.com> + 99 others);
        Tue, 26 May 2020 21:01:29 -0400
Received: from mail.kernel.org ([198.145.29.99]:33090 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726701AbgE0BB2 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 26 May 2020 21:01:28 -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 E70632089D;
        Wed, 27 May 2020 01:01:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1590541288;
        bh=JrTsD2iMGSvX30rQ6pUzDT7ruFhGoJkwwO5nT3DHnLA=;
        h=In-Reply-To:References:Subject:From:Cc:To:Date:From;
        b=Xh1Jo2Y4Mbkg3kJQBo5E2lYeVqbAgpqo9Onjsn1QU4qm6YWCUir0yIBPaQbBHS1MY
         0Z5oVez97RqsKUe6ruh4K4RAS5rkdpTJuSDwUE1QDfRCKzlpT00QCXvgK9sZn1ls+v
         g6p8BD9BUImzfnTkpzysszKJ4AL1VH6T9j6iDh5Y=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1583185843-20707-4-git-send-email-jolly.shah@xilinx.com>
References: <1583185843-20707-1-git-send-email-jolly.shah@xilinx.com> <1583185843-20707-4-git-send-email-jolly.shah@xilinx.com>
Subject: Re: [PATCH v2 3/4] drivers: clk: zynqmp: Fix invalid clock name queries
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     rajanv@xilinx.com, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org, Rajan Vaja <rajan.vaja@xilinx.com>,
        Tejas Patel <tejas.patel@xilinx.com>,
        Jolly Shah <jolly.shah@xilinx.com>
To:     Jolly Shah <jolly.shah@xilinx.com>, arm@kernel.org,
        linux-clk@vger.kernel.org, michal.simek@xilinx.com,
        mturquette@baylibre.com, olof@lixom.net
Date:   Tue, 26 May 2020 18:01:27 -0700
Message-ID: <159054128731.88029.11937261949939343886@swboyd.mtv.corp.google.com>
User-Agent: alot/0.9
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Quoting Jolly Shah (2020-03-02 13:50:42)
> From: Rajan Vaja <rajan.vaja@xilinx.com>
>=20
> The clock driver makes EEMI call to get the name of invalid clk
> when executing versal_get_clock_info() function. This results in
> error messages.
> Added check for validating clock before saving clock attribute and
> calling zynqmp_pm_clock_get_name() in versal_get_clock_info() function.
>=20
> Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
> Signed-off-by: Tejas Patel <tejas.patel@xilinx.com>
> Signed-off-by: Jolly Shah <jolly.shah@xilinx.com>
> ---

Applied to clk-next