On Tue, Sep 3, 2019 at 3:27 PM Palmer Dabbelt <[email protected]> wrote: > > On Wed, 28 Aug 2019 10:52:05 PDT (-0700), [email protected] wrote: > > > > > >> On Aug 25, 2019, at 2:59 PM, Kees Cook <[email protected]> wrote: > >> > >>> On Thu, Aug 22, 2019 at 01:55:22PM -0700, David Abdurachmanov wrote: > >>> This patch was extensively tested on Fedora/RISCV (applied by default on > >>> top of 5.2-rc7 kernel for <2 months). The patch was also tested with > >>> 5.3-rc > >>> on QEMU and SiFive Unleashed board. > >> > >> Oops, I see the mention of QEMU here. Where's the best place to find > >> instructions on creating a qemu riscv image/environment? > > > > I don’t suppose one of you riscv folks would like to contribute riscv > > support to virtme? virtme-run —arch=riscv would be quite nice, and the > > total patch should be just a couple lines. Unfortunately, it helps a lot > > to understand the subtleties of booting the architecture to write those > > couple lines :) > > What mailing list should I sent this to? You need to use the "virtme" branch > of kernel.org/palmer/linux.git until I send the defconfig patches. > > commit a8bd7b318691891991caea298f9a5ed0f815c322 > gpg: Signature made Tue 03 Sep 2019 03:22:45 PM PDT > gpg: using RSA key 00CE76D1834960DFCE886DF8EF4CA1502CCBAB41 > gpg: issuer "[email protected]" > gpg: Good signature from "Palmer Dabbelt <[email protected]>" [ultimate] > gpg: aka "Palmer Dabbelt <[email protected]>" [ultimate] > Author: Palmer Dabbelt <[email protected]> > Date: Tue Sep 3 14:39:39 2019 -0700 > > Add RISC-V support
Could you rebase onto virtme master and resend in some format that isn't corrupt? git am really doesn't like your patch and, even if I fix it up manually, your gpg: lines are bogus. You could also send a PR at https://github.com/amluto/virtme
