Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Lukas Bulwahn <lukas.bulwahn@gmail.com>
To:     Michael Turquette <mturquette@baylibre.com>,
        Stephen Boyd <sboyd@kernel.org>, Joe Perches <joe@perches.com>,
        linux-clk@vger.kernel.org
Cc:     Luca Ceresoli <luca@lucaceresoli.net>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Charles Keepax <ckeepax@opensource.cirrus.com>,
        Richard Fitzgerald <rf@opensource.cirrus.com>,
        devicetree@vger.kernel.org, patches@opensource.cirrus.com,
        kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
        Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH 0/2] Move headers from dt-bindings/clk to clock
Date:   Mon, 13 Jun 2022 10:16:30 +0200
Message-Id: <20220613081632.2159-1-lukas.bulwahn@gmail.com>
Precedence: bulk

Michael, Stephen,

I was investigating the state of ownership of the files in
include/dt-bindings/ according to the MAINTAINERS file and noticed that
there are two directories, clk and clock, that contain the include files
for clock drivers mentioned in dt-bindings.

It seems that by mistake, files were added to include/dt-bindings/clk/
instead of include/dt-bindings/clock/ where the majority of files are
located.

In the past, others already took care of moving some files from
clk to clock in the commit 8e28918a85a0 ("dt-bindings: clock: Move
ti-dra7-atl.h to dt-bindings/clock") and commit 35d35aae8177
("dt-bindings: clock: Move at91.h to dt-bindigs/clock").

This patch series repeats this activity of moving files from clk to clock
for the latest state of the kernel repository.

Michael, Stephen, please pick this minor clean-up patches into your common
clock tree.

The references that needed to be adapted was identified with git grep;
I have not compile-tested these patches and I am relying that the
specific compile-test builds for these drivers will detect any potential
issues with this refactoring.


Joe, I was also considering to create a rule in checkpatch.pl to check if a
patch creates some file in and warn about it. What do you think? You think
this is worth a rule in checkpatch? If so, I will create a first RFC patch
for such a rule.


Best regards,

Lukas


Lukas Bulwahn (2):
  dt-bindings: clock: Move lochnagar.h to dt-bindings/clock
  dt-bindings: clock: Move versaclock.h to dt-bindings/clock

 Documentation/devicetree/bindings/clock/idt,versaclock5.yaml | 4 ++--
 Documentation/devicetree/bindings/mfd/cirrus,lochnagar.yaml  | 2 +-
 MAINTAINERS                                                  | 2 +-
 arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi    | 2 +-
 arch/arm64/boot/dts/renesas/beacon-renesom-som.dtsi          | 2 +-
 drivers/clk/clk-lochnagar.c                                  | 2 +-
 drivers/clk/clk-versaclock5.c                                | 2 +-
 include/dt-bindings/{clk => clock}/lochnagar.h               | 0
 include/dt-bindings/{clk => clock}/versaclock.h              | 0
 9 files changed, 8 insertions(+), 8 deletions(-)
 rename include/dt-bindings/{clk => clock}/lochnagar.h (100%)
 rename include/dt-bindings/{clk => clock}/versaclock.h (100%)

-- 
2.17.1