From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Rob Herring <robh@kernel.org>
Cc: pierre-henry.moussay@microchip.com,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Daire McNamara <daire.mcnamara@microchip.com>,
Lewis Hanly <lewis.hanly@microchip.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: rtc: mpfs-rtc: Properly name file
Date: Mon, 14 Oct 2024 18:54:03 +0200 [thread overview]
Message-ID: <20241014165403e640f637@mail.local> (raw)
In-Reply-To: <CAL_JsqL=OJss3kudaQBx==g2zBiqtsbWJZ5oOFWJF-vLCQZ+yg@mail.gmail.com>
On 14/10/2024 10:39:20-0500, Rob Herring wrote:
> On Fri, Oct 11, 2024 at 5:06 AM <alexandre.belloni@bootlin.com> wrote:
> >
> > From: Alexandre Belloni <alexandre.belloni@bootlin.com>
> >
> > The actual compatible string is microchip,mpfs-rtc, not microchip,mfps-rtc.
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > ---
> > .../rtc/{microchip,mfps-rtc.yaml => microchip,mpfs-rtc.yaml} | 0
> > 1 file changed, 0 insertions(+), 0 deletions(-)
> > rename Documentation/devicetree/bindings/rtc/{microchip,mfps-rtc.yaml => microchip,mpfs-rtc.yaml} (100%)
> >
> > diff --git a/Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml b/Documentation/devicetree/bindings/rtc/microchip,mpfs-rtc.yaml
> > similarity index 100%
> > rename from Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml
> > rename to Documentation/devicetree/bindings/rtc/microchip,mpfs-rtc.yaml
>
> Incomplete. Now next has this warning:
>
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/rtc/microchip,mpfs-rtc.yaml:
> $id: Cannot determine base path from $id, relative path/filename
> doesn't match actual path or filename
> $id: http://devicetree.org/schemas/rtc/microchip,mfps-rtc.yaml
> file: /builds/robherring/linux-dt/Documentation/devicetree/bindings/rtc/microchip,mpfs-rtc.yaml
I fixed it directly in my tree...
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-10-14 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 10:06 [PATCH] dt-bindings: rtc: mpfs-rtc: Properly name file alexandre.belloni
2024-10-11 10:34 ` Conor Dooley
2024-10-14 15:39 ` Rob Herring
2024-10-14 16:54 ` Alexandre Belloni [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=20241014165403e640f637@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lewis.hanly@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=pierre-henry.moussay@microchip.com \
--cc=robh@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 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).