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-rc6 Date: Fri, 29 Apr 2022 09:38:55 -0700 (PDT) [thread overview] Message-ID: <mhng-23ee08e3-f500-4297-bd05-a1902598d9b3@palmer-ri-x1c9> (raw) The following changes since commit bf9bac40b7635e2ce43ba0051a64c3fd44312405: RISC-V: cpuidle: fix Kconfig select for RISCV_SBI_CPUIDLE (2022-04-21 15:10:47 -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-rc5 for you to fetch changes up to ac0280a9ca106c5501257e79d165f968712b5899: RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL (2022-04-26 08:19:53 -0700) ---------------------------------------------------------------- RISC-V Fixes for 5.18-rc6 * A fix to properly ensure a single CPU is running during patch_text(). * A defconfig update to include RPMSG_CTRL when RPMSG_CHAR was set, necessary after a recent refactoring. ---------------------------------------------------------------- Arnaud Pouliquen (1): RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL Guo Ren (1): riscv: patch_text: Fixup last cpu should be master arch/riscv/configs/defconfig | 1 + arch/riscv/configs/rv32_defconfig | 1 + arch/riscv/kernel/patch.c | 2 +- 3 files changed, 3 insertions(+), 1 deletion(-)
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-rc6 Date: Fri, 29 Apr 2022 09:38:55 -0700 (PDT) [thread overview] Message-ID: <mhng-23ee08e3-f500-4297-bd05-a1902598d9b3@palmer-ri-x1c9> (raw) The following changes since commit bf9bac40b7635e2ce43ba0051a64c3fd44312405: RISC-V: cpuidle: fix Kconfig select for RISCV_SBI_CPUIDLE (2022-04-21 15:10:47 -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-rc5 for you to fetch changes up to ac0280a9ca106c5501257e79d165f968712b5899: RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL (2022-04-26 08:19:53 -0700) ---------------------------------------------------------------- RISC-V Fixes for 5.18-rc6 * A fix to properly ensure a single CPU is running during patch_text(). * A defconfig update to include RPMSG_CTRL when RPMSG_CHAR was set, necessary after a recent refactoring. ---------------------------------------------------------------- Arnaud Pouliquen (1): RISC-V: configs: Configs that had RPMSG_CHAR now get RPMSG_CTRL Guo Ren (1): riscv: patch_text: Fixup last cpu should be master arch/riscv/configs/defconfig | 1 + arch/riscv/configs/rv32_defconfig | 1 + arch/riscv/kernel/patch.c | 2 +- 3 files changed, 3 insertions(+), 1 deletion(-) _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-04-29 16:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-29 16:38 Palmer Dabbelt [this message] 2022-04-29 16:38 ` [GIT PULL] RISC-V Fixes for 5.18-rc6 Palmer Dabbelt 2022-04-29 17:47 ` pr-tracker-bot 2022-04-29 17:47 ` 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-23ee08e3-f500-4297-bd05-a1902598d9b3@palmer-ri-x1c9 \ --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: 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.