From: Rob Herring <robh+dt@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Przemysław Gaj" <pgaj@cadence.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Vitor Soares" <vitor.soares@synopsys.com>,
devicetree@vger.kernel.org, linux-i3c@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 27/32] dt-bindings: i3c: update i3c.yaml references
Date: Tue, 6 Apr 2021 10:05:47 -0500 [thread overview]
Message-ID: <CAL_Jsq+d9nU8r_1tvrU9Yk4rCN3fve6D29JMLFN59jJxLWjhrA@mail.gmail.com> (raw)
In-Reply-To: <22b7b53af1907f7cae27e26be725470c04b84725.1617279356.git.mchehab+huawei@kernel.org>
On Thu, Apr 1, 2021 at 7:17 AM Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Changeset 5e4cdca887fd ("dt-bindings: i3c: Convert the bus description to yaml")
> renamed: Documentation/devicetree/bindings/i3c/i3c.txt
> to: Documentation/devicetree/bindings/i3c/i3c.yaml.
>
> Update the cross-references accordingly.
>
> Fixes: 5e4cdca887fd ("dt-bindings: i3c: Convert the bus description to yaml")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/devicetree/bindings/i3c/cdns,i3c-master.txt | 6 +++---
> .../devicetree/bindings/i3c/snps,dw-i3c-master.txt | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
Ugg, I should have remembered this...
Acked-by: Rob Herring <robh@kernel.org>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2021-04-06 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 12:17 [PATCH 00/32] Fix broken documentation file references Mauro Carvalho Chehab
2021-04-01 12:17 ` [PATCH 27/32] dt-bindings: i3c: update i3c.yaml references Mauro Carvalho Chehab
2021-04-06 15:05 ` 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=CAL_Jsq+d9nU8r_1tvrU9Yk4rCN3fve6D29JMLFN59jJxLWjhrA@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=pgaj@cadence.com \
--cc=vitor.soares@synopsys.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).