From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <devicetree-owner@vger.kernel.org>
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 4583FC61DA4
	for <linux-devicetree@archiver.kernel.org>; Mon,  6 Mar 2023 22:18:42 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229943AbjCFWSl (ORCPT
        <rfc822;linux-devicetree@archiver.kernel.org>);
        Mon, 6 Mar 2023 17:18:41 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45368 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229700AbjCFWSk (ORCPT
        <rfc822;devicetree@vger.kernel.org>); Mon, 6 Mar 2023 17:18:40 -0500
Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6F548136EB;
        Mon,  6 Mar 2023 14:18:39 -0800 (PST)
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 0C35760DB9;
        Mon,  6 Mar 2023 22:18:39 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5F939C4339B;
        Mon,  6 Mar 2023 22:18:38 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1678141118;
        bh=I3JsmSN8AuRtmoJfdfkuN27L++0qhlJt/ugpaFFonqw=;
        h=In-Reply-To:References:Subject:From:Cc:To:Date:From;
        b=T3xgxA3myeLBnU6Yz/emcCg8vNlP//EBvb656NiaARrDpBGFRKedojWXm4hmy8o37
         KKAdzP0vxDAPfZZGUA8wAOwxq9hbPMjlK7Z/KJ7PdMhfn6xlhzDscWBm5ePZQV2jPz
         r1uvqtvre8dyw9WdBWVYHJkURVOQYzj+10is6q2/lRZYj8tCPcp35wRbmc3FHUGRjG
         YvQ8pbuXLAFYksKDpFR0FH6EGH5Cb7JbOpe+L2+lhlSyt/KTBiDUGAkqZ0ALStrqtt
         85WtXUjGiHcnC+VO+Zisg8JPlQeePSEvUslrL9A2Q/lYrV/zQFMH91Hw67RjklNik3
         +j6uyShsq2R3Q==
Message-ID: <9f6866f9eb097c0ca1c9d8fd8586c9e7.sboyd@kernel.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20230302005834.13171-5-jk@codeconstruct.com.au>
References: <20230302005834.13171-1-jk@codeconstruct.com.au> <20230302005834.13171-5-jk@codeconstruct.com.au>
Subject: Re: [PATCH v5 4/6] dt-bindings: clock: ast2600: remove IC36 & I3C7 clock definitions
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Michael Turquette <mturquette@baylibre.com>,
        Rob Herring <robh+dt@kernel.org>,
        Dylan Hung <dylan_hung@aspeedtech.com>,
        Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
To:     Jeremy Kerr <jk@codeconstruct.com.au>, devicetree@vger.kernel.org,
        linux-aspeed@lists.ozlabs.org, linux-clk@vger.kernel.org
Date:   Mon, 06 Mar 2023 14:18:36 -0800
User-Agent: alot/0.10
Precedence: bulk
List-ID: <devicetree.vger.kernel.org>
X-Mailing-List: devicetree@vger.kernel.org

Quoting Jeremy Kerr (2023-03-01 16:58:32)
> The current ast2600 clock definitions include entries for i3c6 and i3c7
> devices, which don't exist: there are no clock control lines documented
> for these, and only i3c devices 0 through 5 are present.
>=20
> So, remove the definitions for I3C6 and I3C7. Although this is a
> potential ABI-breaking change, there are no in-tree users of these, and
> any references would be broken anyway, as the hardware doesn't exist.
>=20
> This is a partial cherry-pick and rework of ed44b8cdfdb and 1a35eb926d7
> from Aspeed's own tree, originally by Dylan Hung
> <dylan_hung@aspeedtech.com>.
>=20
> Reviewed-by: Joel Stanley <joel@jms.id.au>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
>=20
> ---

Applied to clk-next