From: Stephen Boyd <sboyd@kernel.org>
To: Joe Perches <joe@perches.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Michael Turquette <mturquette@baylibre.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: Re: [PATCH 2/2] dt-bindings: clock: Move versaclock.h to dt-bindings/clock
Date: Mon, 22 Aug 2022 16:07:08 -0700 [thread overview]
Message-ID: <20220822230710.85E18C433C1@smtp.kernel.org> (raw)
In-Reply-To: <20220613081632.2159-3-lukas.bulwahn@gmail.com>
Quoting Lukas Bulwahn (2022-06-13 01:16:32)
> Most of the clock related dt-binding header files are located in
> dt-bindings/clock folder. It would be good to keep all the similar
> header files at a single location.
>
> This was discovered while investigating the state of ownership of the
> files in include/dt-bindings/ according to the MAINTAINERS file.
>
> This change here is similar to 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").
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2022-08-22 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 8:16 [PATCH 0/2] Move headers from dt-bindings/clk to clock Lukas Bulwahn
2022-06-13 8:16 ` [PATCH 1/2] dt-bindings: clock: Move lochnagar.h to dt-bindings/clock Lukas Bulwahn
2022-06-13 9:52 ` Charles Keepax
2022-06-16 15:14 ` Rob Herring
2022-08-22 23:06 ` Stephen Boyd
2022-06-13 8:16 ` [PATCH 2/2] dt-bindings: clock: Move versaclock.h " Lukas Bulwahn
2022-06-13 20:53 ` Luca Ceresoli
2022-06-16 15:14 ` Rob Herring
2022-08-22 23:07 ` Stephen Boyd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220822230710.85E18C433C1@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=lukas.bulwahn@gmail.com \
--cc=mturquette@baylibre.com \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.