From: Sean Christopherson <seanjc@google.com>
To: Anup Patel <Anup.Patel@wdc.com>
Cc: Adam Borowski <kilobyte@angband.pl>,
Atish Patra <atishp@atishpatra.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
"kvm-riscv@lists.infradead.org" <kvm-riscv@lists.infradead.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: ERROR: modpost: "boot_cpu_hartid" [arch/riscv/kvm/kvm.ko] undefined!
Date: Mon, 29 Nov 2021 21:23:59 +0000 [thread overview]
Message-ID: <YaVE775RaGQJsysE@google.com> (raw)
In-Reply-To: <956FCFEA-AB88-495B-B4CD-F3FB410A4270@wdc.com>
On Tue, Nov 23, 2021, Anup Patel wrote:
> @Sean, can you re-send this patch to the Linux RISC-V mailing list ? It
> seems this email did not land correctly for Atish and other folks.
Yep, I'll get it posted, sorry for the delay.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2021-11-29 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:14 ERROR: modpost: "boot_cpu_hartid" [arch/riscv/kvm/kvm.ko] undefined! Adam Borowski
2021-11-22 18:34 ` Sean Christopherson
2021-11-23 5:33 ` Anup Patel
2021-11-23 15:07 ` Atish Patra
2021-11-29 21:23 ` Sean Christopherson [this message]
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=YaVE775RaGQJsysE@google.com \
--to=seanjc@google.com \
--cc=Anup.Patel@wdc.com \
--cc=atishp@atishpatra.org \
--cc=kilobyte@angband.pl \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
/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