From: Conor Dooley <conor@kernel.org> To: arnd@arndb.de Cc: conor@kernel.org, palmer@dabbelt.com, linux-riscv@lists.infradead.org, soc@kernel.org Subject: [GIT PULL] RISC-V Devicetree fixes for v6.3-final Date: Thu, 6 Apr 2023 18:36:56 +0100 [thread overview] Message-ID: <20230406-negate-octagon-0fc2e47dbde5@spud> (raw) [-- Attachment #1: Type: text/plain, Size: 1245 bytes --] Hey Arnd, Please pull a single fix, it's been a quiet window on the fixes front! I don't have any urgent fixes on the soc side either, only fixes for behaviour that cannot be triggered with an upstream kernel that I've put in for-next. Thanks, Conor. The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6: Linux 6.3-rc1 (2023-03-05 14:52:03 -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.3-final for you to fetch changes up to 8056dc043d7f74d7675d413cb3dc4fa290609922: riscv: dts: canaan: drop invalid spi-max-frequency (2023-03-26 23:58:27 +0100) ---------------------------------------------------------------- RISC-V Devicetree fixes for v6.3-final A solitary fix here from Krzysztof for an invalid property that should've probably been removed months ago, but was missed due to it being in a dtb that doesn't build w/ defconfig. Signed-off-by: Conor Dooley <conor.dooley@microchip.com> ---------------------------------------------------------------- Krzysztof Kozlowski (1): riscv: dts: canaan: drop invalid spi-max-frequency arch/riscv/boot/dts/canaan/k210.dtsi | 1 - 1 file changed, 1 deletion(-) [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org> To: arnd@arndb.de Cc: conor@kernel.org, palmer@dabbelt.com, linux-riscv@lists.infradead.org, soc@kernel.org Subject: [GIT PULL] RISC-V Devicetree fixes for v6.3-final Date: Thu, 6 Apr 2023 18:36:56 +0100 [thread overview] Message-ID: <20230406-negate-octagon-0fc2e47dbde5@spud> (raw) [-- Attachment #1.1: Type: text/plain, Size: 1245 bytes --] Hey Arnd, Please pull a single fix, it's been a quiet window on the fixes front! I don't have any urgent fixes on the soc side either, only fixes for behaviour that cannot be triggered with an upstream kernel that I've put in for-next. Thanks, Conor. The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6: Linux 6.3-rc1 (2023-03-05 14:52:03 -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.3-final for you to fetch changes up to 8056dc043d7f74d7675d413cb3dc4fa290609922: riscv: dts: canaan: drop invalid spi-max-frequency (2023-03-26 23:58:27 +0100) ---------------------------------------------------------------- RISC-V Devicetree fixes for v6.3-final A solitary fix here from Krzysztof for an invalid property that should've probably been removed months ago, but was missed due to it being in a dtb that doesn't build w/ defconfig. Signed-off-by: Conor Dooley <conor.dooley@microchip.com> ---------------------------------------------------------------- Krzysztof Kozlowski (1): riscv: dts: canaan: drop invalid spi-max-frequency arch/riscv/boot/dts/canaan/k210.dtsi | 1 - 1 file changed, 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
next reply other threads:[~2023-04-06 17:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-06 17:36 Conor Dooley [this message] 2023-04-06 17:36 ` [GIT PULL] RISC-V Devicetree fixes for v6.3-final Conor Dooley 2023-04-06 21:30 ` patchwork-bot+linux-soc 2023-04-06 21:30 ` patchwork-bot+linux-soc
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=20230406-negate-octagon-0fc2e47dbde5@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: linkBe 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.