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;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1594739122-29327-1-git-send-email-sivaprak@codeaurora.org>
References: <1594739122-29327-1-git-send-email-sivaprak@codeaurora.org>
Subject: Re: [PATCH 0/4] Split ipq8074 reset bindings from clock bindings
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     Sivaprakash Murugesan <sivaprak@codeaurora.org>
To:     Sivaprakash Murugesan <sivaprak@codeaurora.org>, agross@kernel.org,
        bjorn.andersson@linaro.org, devicetree@vger.kernel.org,
        linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
        linux-kernel@vger.kernel.org, mturquette@baylibre.com,
        p.zabel@pengutronix.de, robh+dt@kernel.org
Date:   Wed, 15 Jul 2020 17:55:12 -0700
Message-ID: <159486091238.1987609.14897518216700398772@swboyd.mtv.corp.google.com>
User-Agent: alot/0.9
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Quoting Sivaprakash Murugesan (2020-07-14 08:05:18)
> The patch series https://lwn.net/Articles/825325/ wrongly added clock
> bindings into reset bindings. This is caught by=20
> kernel test robot <lkp@intel.com> after it got merged into the clk-next
> tree.
>=20
> To avoid these kind of future mistakes it is better we split up the reset
> bindings from clock bindings.
>=20
> Since the clock patches in https://lwn.net/Articles/825325/ are applied to
> clk-next it would be better if all the changes in this series to go throu=
gh
> clk-next.

I disagree. We've put them all in the same file because they're all used
provided by the same compatible string. Please keep doing that and just
fix the number scheme if that is the problem. Also, use lore.kernel.org
for your links next time (i.e. https://lore.kernel.org/r/<message-id>)
so that we don't need to rely on lwn.net links.