From: Conor Dooley <conor@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
conor@kernel.org, soc@kernel.org
Subject: [GIT PULL] RISC-V DT for v6.2-rc4
Date: Wed, 11 Jan 2023 21:35:27 +0000 [thread overview]
Message-ID: <Y78rn+0fVNOxHLKt@spud> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]
Hey Arnd!
Been a quiet period since -rc1, so I only have a single DT fix for you.
Figured I'd get it out of the way & write the script that I've been
meaning to write since I sent the first pair of PRs at the same time.
Hopefully I didn't break anything in the process!
Thanks,
Conor.
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/riscv-dt-fixes-for-v6.2-rc4
for you to fetch changes up to 43d5f5d63699724d47f0d9e0eae516a260d232b4:
riscv: dts: sifive: fu740: fix size of pcie 32bit memory (2023-01-07 19:31:37 +0000)
----------------------------------------------------------------
RISC-V DeviceTrees for v6.2
SiFive:
A solitary fix for the PCI memory regions on the unmatched, triggered by
an SM768. No-one must have tried one until just recently!
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Ben Dooks (1):
riscv: dts: sifive: fu740: fix size of pcie 32bit memory
arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2023-01-11 21:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y78rn+0fVNOxHLKt@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=soc@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