From: Rob Herring <robh@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: devicetree@vger.kernel.org,
Aditya Srivastava <yashsri421@gmail.com>,
Wei Xu <xuwei5@hisilicon.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devicetree: replace invalid kernel-doc comment headers
Date: Wed, 24 Mar 2021 13:59:51 -0600 [thread overview]
Message-ID: <20210324195951.GA3526633@robh.at.kernel.org> (raw)
In-Reply-To: <20210322072343.19993-1-lukas.bulwahn@gmail.com>
On Mon, Mar 22, 2021 at 08:23:43AM +0100, Lukas Bulwahn wrote:
> The opening comment mark '/**' is used for indicating the beginning of
> kernel-doc comments.
>
> Replace uses of '/**' for invalid cases in dt-binding headers and dts.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Rob, please pick this quick kernel-doc cleanup patch.
dts files don't go thru my tree. Please split this into 2 patches.
>
> arch/arm64/boot/dts/hisilicon/hip05-d02.dts | 2 +-
> arch/arm64/boot/dts/hisilicon/hip05.dtsi | 2 +-
> arch/arm64/boot/dts/hisilicon/hip06-d03.dts | 2 +-
> arch/arm64/boot/dts/hisilicon/hip06.dtsi | 4 ++--
> arch/arm64/boot/dts/hisilicon/hip07-d05.dts | 2 +-
> arch/arm64/boot/dts/hisilicon/hip07.dtsi | 2 +-
> include/dt-bindings/reset/hisi,hi6220-resets.h | 2 +-
> include/dt-bindings/reset/snps,hsdk-reset.h | 2 +-
> 8 files changed, 9 insertions(+), 9 deletions(-)
prev parent reply other threads:[~2021-03-24 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 7:23 [PATCH] devicetree: replace invalid kernel-doc comment headers Lukas Bulwahn
2021-03-22 18:46 ` Randy Dunlap
2021-03-24 19:59 ` Rob Herring [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=20210324195951.GA3526633@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=xuwei5@hisilicon.com \
--cc=yashsri421@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).