All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.18
Date: Fri, 20 May 2022 08:42:22 -0700 (PDT)	[thread overview]
Message-ID: <mhng-d5b7ee6d-8d8f-4603-9a20-843f35fae857@palmer-mbp2014> (raw)

The following changes since commit c6fe81191bd74f7e6ae9ce96a4837df9485f3ab8:

  RISC-V: relocate DTB if it's outside memory region (2022-04-29 07:59:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.18-rc8

for you to fetch changes up to c932edeaf6d6e6cc25088e61c3fcf585c30497c0:

  riscv: dts: microchip: fix gpio1 reg property typo (2022-05-19 16:47:29 -0700)

----------------------------------------------------------------
RISC-V Fixes for 5.18

* A fix for the fu540-c000 device tree to avoid a schema check failure
  on the DMA node name.
* A fix to the PolarFire SOC device tree for a typo.

----------------------------------------------------------------
Neither of these is particularly high impact so no big deal if it's too late
for 5.18, but I figured there's no reason to wait as they're also very unlikely
to break anything.

----------------------------------------------------------------
Conor Paxton (1):
      riscv: dts: microchip: fix gpio1 reg property typo

Krzysztof Kozlowski (1):
      riscv: dts: sifive: fu540-c000: align dma node name with dtschema

 arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi | 2 +-
 arch/riscv/boot/dts/sifive/fu540-c000.dtsi        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org,        linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.18
Date: Fri, 20 May 2022 08:42:22 -0700 (PDT)	[thread overview]
Message-ID: <mhng-d5b7ee6d-8d8f-4603-9a20-843f35fae857@palmer-mbp2014> (raw)

The following changes since commit c6fe81191bd74f7e6ae9ce96a4837df9485f3ab8:

  RISC-V: relocate DTB if it's outside memory region (2022-04-29 07:59:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.18-rc8

for you to fetch changes up to c932edeaf6d6e6cc25088e61c3fcf585c30497c0:

  riscv: dts: microchip: fix gpio1 reg property typo (2022-05-19 16:47:29 -0700)

----------------------------------------------------------------
RISC-V Fixes for 5.18

* A fix for the fu540-c000 device tree to avoid a schema check failure
  on the DMA node name.
* A fix to the PolarFire SOC device tree for a typo.

----------------------------------------------------------------
Neither of these is particularly high impact so no big deal if it's too late
for 5.18, but I figured there's no reason to wait as they're also very unlikely
to break anything.

----------------------------------------------------------------
Conor Paxton (1):
      riscv: dts: microchip: fix gpio1 reg property typo

Krzysztof Kozlowski (1):
      riscv: dts: sifive: fu540-c000: align dma node name with dtschema

 arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi | 2 +-
 arch/riscv/boot/dts/sifive/fu540-c000.dtsi        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

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

             reply	other threads:[~2022-05-20 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 15:42 Palmer Dabbelt [this message]
2022-05-20 15:42 ` [GIT PULL] RISC-V Fixes for 5.18 Palmer Dabbelt
2022-05-20 18:36 ` pr-tracker-bot
2022-05-20 18:36   ` pr-tracker-bot

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=mhng-d5b7ee6d-8d8f-4603-9a20-843f35fae857@palmer-mbp2014 \
    --to=palmer@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=torvalds@linux-foundation.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 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.