From: patchwork-bot+linux-riscv@kernel.org
To: Guo Ren <guoren@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@rivosinc.com,
conor.dooley@microchip.com, liaochang1@huawei.com,
lizhengyu3@huawei.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, guoren@linux.alibaba.com,
conor@kernel.org, lkp@intel.com
Subject: Re: [PATCH] riscv: Fixup compile error with !MMU
Date: Tue, 13 Dec 2022 17:40:17 +0000 [thread overview]
Message-ID: <167095321743.5951.3619740095349418774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221207091112.2258674-1-guoren@kernel.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 7 Dec 2022 04:11:12 -0500 you wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> Current nommu_virt_defconfig can't compile:
>
> In file included from
> arch/riscv/kernel/crash_core.c:3:
> arch/riscv/kernel/crash_core.c:
> In function 'arch_crash_save_vmcoreinfo':
> arch/riscv/kernel/crash_core.c:8:27:
> error: 'VA_BITS' undeclared (first use in this function)
> 8 | VMCOREINFO_NUMBER(VA_BITS);
> | ^~~~~~~
>
> [...]
Here is the summary with links:
- riscv: Fixup compile error with !MMU
https://git.kernel.org/riscv/c/c528ef0888b7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-13 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:11 [PATCH] riscv: Fixup compile error with !MMU guoren
2022-12-07 9:32 ` Conor Dooley
2022-12-07 14:01 ` Guo Ren
2022-12-13 17:39 ` Palmer Dabbelt
2022-12-13 17:40 ` patchwork-bot+linux-riscv [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=167095321743.5951.3619740095349418774.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=liaochang1@huawei.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lizhengyu3@huawei.com \
--cc=lkp@intel.com \
--cc=palmer@rivosinc.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