All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Anup Patel <anup.patel@wdc.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH v4 0/2] dt-bindings: timer: sifive, clint: Miscellaneous improvements
Date: Fri, 28 Jan 2022 10:07:34 +0100	[thread overview]
Message-ID: <cover.1643360652.git.geert@linux-m68k.org> (raw)

	Hi all,

This patch series contains two improvements for the SiFive CLINT DT
bindings.

Changes compared to v3[1]:
  - Use architectural maximum instead of practical maximum of 10,
  - Add Reviewed-by (this time for real ;-).

Changes compared to v2[2]:
  - Add Acked-by, Reviewed-by.

Changes compared to v1[3]:
  - Split in two patches,
  - Improve patch description and document limit rationale.

Thanks!

[1] https://lore.kernel.org/r/cover.1639744468.git.geert@linux-m68k.org/
[2] https://lore.kernel.org/r/cover.1639662093.git.geert@linux-m68k.org
[3] https://lore.kernel.org/r/20211125152317.162958-1-geert@linux-m68k.org

Geert Uytterhoeven (2):
  dt-bindings: timer: sifive,clint: Fix number of interrupts
  dt-bindings: timer: sifive,clint: Group interrupt tuples

 .../devicetree/bindings/timer/sifive,clint.yaml          | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

-- 
2.25.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Anup Patel <anup.patel@wdc.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH v4 0/2] dt-bindings: timer: sifive, clint: Miscellaneous improvements
Date: Fri, 28 Jan 2022 10:07:34 +0100	[thread overview]
Message-ID: <cover.1643360652.git.geert@linux-m68k.org> (raw)

	Hi all,

This patch series contains two improvements for the SiFive CLINT DT
bindings.

Changes compared to v3[1]:
  - Use architectural maximum instead of practical maximum of 10,
  - Add Reviewed-by (this time for real ;-).

Changes compared to v2[2]:
  - Add Acked-by, Reviewed-by.

Changes compared to v1[3]:
  - Split in two patches,
  - Improve patch description and document limit rationale.

Thanks!

[1] https://lore.kernel.org/r/cover.1639744468.git.geert@linux-m68k.org/
[2] https://lore.kernel.org/r/cover.1639662093.git.geert@linux-m68k.org
[3] https://lore.kernel.org/r/20211125152317.162958-1-geert@linux-m68k.org

Geert Uytterhoeven (2):
  dt-bindings: timer: sifive,clint: Fix number of interrupts
  dt-bindings: timer: sifive,clint: Group interrupt tuples

 .../devicetree/bindings/timer/sifive,clint.yaml          | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

-- 
2.25.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2022-01-28  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  9:07 Geert Uytterhoeven [this message]
2022-01-28  9:07 ` [PATCH v4 0/2] dt-bindings: timer: sifive, clint: Miscellaneous improvements Geert Uytterhoeven
2022-01-28  9:07 ` [PATCH v4 1/2] dt-bindings: timer: sifive, clint: Fix number of interrupts Geert Uytterhoeven
2022-01-28  9:07   ` [PATCH v4 1/2] dt-bindings: timer: sifive,clint: " Geert Uytterhoeven
2022-01-28 13:16   ` [PATCH v4 1/2] dt-bindings: timer: sifive, clint: " Anup Patel
2022-01-28 13:16     ` Anup Patel
2022-01-28 17:55   ` Conor Dooley
2022-01-28 17:55     ` Conor Dooley
2022-01-28  9:07 ` [PATCH v4 2/2] dt-bindings: timer: sifive, clint: Group interrupt tuples Geert Uytterhoeven
2022-01-28  9:07   ` [PATCH v4 2/2] dt-bindings: timer: sifive,clint: " Geert Uytterhoeven
2022-01-28 13:17   ` [PATCH v4 2/2] dt-bindings: timer: sifive, clint: " Anup Patel
2022-01-28 13:17     ` Anup Patel
2022-02-28 19:57 ` [PATCH v4 0/2] dt-bindings: timer: sifive, clint: Miscellaneous improvements Rob Herring
2022-02-28 19:57   ` Rob Herring

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=cover.1643360652.git.geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=anup.patel@wdc.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.