From: Conor Dooley <conor@kernel.org>
To: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
linux-riscv@lists.infradead.org,
Kanak Shilledar <kanakshilledar111@protonmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Samuel Holland <samuel.holland@sifive.com>
Subject: Re: [PATCH 2/2] dt-bindings: riscv: cpus: add ref to interrupt-controller
Date: Mon, 20 May 2024 18:04:02 +0100 [thread overview]
Message-ID: <20240520-verbally-vibes-47604636b8db@spud> (raw)
In-Reply-To: <CAGLn_=tLdJU1F-i9YV5aCZQbS0L7y7Wu+_k6Dn=6HwH5JmZoMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3487 bytes --]
On Mon, May 20, 2024 at 03:09:44PM +0530, Kanak Shilledar wrote:
> On Mon, May 20, 2024 at 1:02 AM Rob Herring (Arm) <robh@kernel.org> wrote:
> >
> >
> > On Sun, 19 May 2024 23:29:06 +0530, Kanak Shilledar wrote:
> > > removed the redundant properties for interrupt-controller
> > > and provide reference to the riscv,cpu-intc.yaml which defines
> > > the interrupt-controller. making the properties for riscv
> > > interrupt-controller at a central place.
> > >
> > > Signed-off-by: Kanak Shilledar <kanakshilledar111@protonmail.com>
> > > ---
> > > .../devicetree/bindings/riscv/cpus.yaml | 22 +------------------
> > > 1 file changed, 1 insertion(+), 21 deletions(-)
> > >
> >
> > My bot found errors running 'make dt_binding_check' on your patch:
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/riscv/cpus.yaml: properties:interrupt-controller: 'oneOf' conditional failed, one must be fixed:
> > Additional properties are not allowed ('$ref' was unexpected)
> > 'type' is a required property
> > hint: DT nodes ("object" type in schemas) can only use a subset of json-schema keywords
> > from schema $id: http://devicetree.org/meta-schemas/interrupts.yaml#
> >
> > doc reference errors (make refcheckdocs):
> >
> > See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240519175906.138410-3-kanakshilledar111@protonmail.com
>
> I have fixed the above warning.
>
> > The base for the series is generally the latest rc1. A different dependency
> > should be noted in *this* patch.
>
> Can you please clarify this part? Is my base commit ID incorrect?
The bot says this in case the error is caused by it having applied
patches on top of 6.9-rc1, but in this case I doubt there's any impact.
By "this patch" it means that having the information in the cover
doesn't help, but info about missing deps should go under the --- line
etc.
| base-commit: 20cb38a7af88dc40095da7c2c9094da3873fea23
| prerequisite-patch-id: 158157d32a32e765834a0cb4fc6335f9009d9962
| prerequisite-patch-id: 4007c7386e66f93b67a2631dddca08cadcee708b
That said, why do you have two prerequisite patches? This applies on top
of 6.9-rc3 without any issues (other than trailing whitespace warnings).
Also, you forgot the v3 tag on this patchset, which confuses tooling:
shazam https://lore.kernel.org/linux-riscv/20240519175906.138410-1-kanakshilledar111@protonmail.com/T/#t
Grabbing thread from lore.kernel.org/all/20240519175906.138410-1-kanakshilledar111@protonmail.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
---> Added from v2: 1 patches
Analyzing 10 messages in the thread
---> Will use the latest revision: v2
You can pick other revisions using the -vN flag
Checking attestation on all messages, may take a moment...
Retrieving CI status, may take a moment...
Some CI checks failed, see patchwork for more info:
https://patchwork.kernel.org/project/linux-riscv/list/?series=854147
---
✓ [● PATCH v2] dt-bindings: interrupt-controller: riscv,cpu-intc: convert to dtschema
+ Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
✓ Signed: DKIM/gmail.com
---
Total patches: 1
---
Applying: dt-bindings: interrupt-controller: riscv,cpu-intc: convert to dtschema
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-20 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 17:59 [PATCH 0/2] dt-bindings: interrupt-controller: riscv,cpu-intc: Kanak Shilledar
2024-05-19 17:59 ` [PATCH 1/2] dt-bindings: interrupt-controller: riscv,cpu-intc: convert to dtschema Kanak Shilledar
2024-05-19 17:59 ` [PATCH 2/2] dt-bindings: riscv: cpus: add ref to interrupt-controller Kanak Shilledar
2024-05-19 19:32 ` Rob Herring (Arm)
2024-05-20 9:39 ` Kanak Shilledar
2024-05-20 17:04 ` Conor Dooley [this message]
2024-05-21 13:56 ` Kanak Shilledar
2024-05-21 18:36 ` Conor Dooley
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=20240520-verbally-vibes-47604636b8db@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kanakshilledar111@protonmail.com \
--cc=kanakshilledar@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).