mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <atulkhare@rivosinc.com>
Cc: <palmer@rivosinc.com>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 0/4] dt-bindings: sifive: fix dt-schema errors
Date: Sun, 5 Jun 2022 12:34:30 +0000	[thread overview]
Message-ID: <fee4c8af-fc80-edaf-0d64-00659b426d42@microchip.com> (raw)
In-Reply-To: <CABMhjYrheOjEYfH7WjmdUj4X=aSbQuUADQ7NNpk0hAjE0LpSxw@mail.gmail.com>

On 21/04/2022 06:07, Atul Khare wrote:
> The patch series fixes dt-schema validation errors that can be reproduced
> using the following: make ARCH=riscv defconfig; make ARCH=riscv
> dt_binding_check dtbs_check

Hey Atul,
I assume you never sent a v2 of these patches?
Could you rebase & resend them with a more complete CC list please?
I think you can drop the microchip dts patch, I didn't see this
series and dropped the clock property myself.

Was trying to clear the errors myself & recalled that Palmer said
you were working on them. Wondered what had happened but this makes
a lot of sense.

Could you also thread the series so that b4 picks it up properly?
Thanks,
Conor.

> 
> 
> Atul Khare (4):
>   dt-bindings: sifive: Support 1024 hart contexts
>   dt-bindings: sifive: add cache-set value of 2048
>   dt-bindings: sifive: delete 'clock' / 'status'
>   dt-bindings: sifive: add gpio-line-names
> 
>  Documentation/devicetree/bindings/gpio/sifive,gpio.yaml      | 3 +++
>  Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 4 +++-
>  Documentation/devicetree/bindings/timer/sifive,clint.yaml    | 2 ++
>  arch/riscv/boot/dts/microchip/microchip-mpfs-icicle-kit.dts  | 4 ----
>  4 files changed, 8 insertions(+), 5 deletions(-)
> 
> --
> 2.35.1

      reply	other threads:[~2022-06-05 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  5:07 Atul Khare
2022-06-05 12:34 ` Conor.Dooley [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=fee4c8af-fc80-edaf-0d64-00659b426d42@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=atulkhare@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.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

all inboxes | Powered by JetHome®