linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>,
	Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: mick@ics.forth.gr, corbet@lwn.net, alexandre.ghiti@canonical.com,
	vgoyal@redhat.com, bhe@redhat.com,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	bagasdotme@gmail.com, dyoung@redhat.com,
	Palmer Dabbelt <palmer@dabbelt.com>,
	heiko@sntech.de, Xianting Tian <xianting.tian@linux.alibaba.com>,
	guoren@kernel.org, anup@brainfault.org, aou@eecs.berkeley.edu,
	hschauhan@nulltrace.org, yixun.lan@gmail.com,
	kexec@lists.infradead.org, heinrich.schuchardt@canonical.com,
	linux-doc@vger.kernel.org, crash-utility@redhat.com,
	linux-kernel@vger.kernel.org, k-hagio-ab@nec.com,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH V5 0/2] Support VMCOREINFO export for RISCV64
Date: Tue, 6 Dec 2022 23:05:06 +0000	[thread overview]
Message-ID: <Y4/KoiFhdvRBDdzH@spud> (raw)
In-Reply-To: <167002857934.4256.16584443879212253129.b4-ty@rivosinc.com>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

Hey Palmer, Xianting,

On Fri, Dec 02, 2022 at 04:49:39PM -0800, Palmer Dabbelt wrote:
> On Wed, 26 Oct 2022 22:42:06 +0800, Xianting Tian wrote:
> > As disscussed in below patch set, the patch of 'describe VMCOREINFO export in Documentation'
> > need to update according to Bagas's comments.
> > https://lore.kernel.org/linux-riscv/22AAF52E-8CC8-4D11-99CB-88DE4D113444@kernel.org/
> > 
> > As others patches in above patch set already applied, so this patch set only contains below two
> > patches.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/2] RISC-V: Add arch_crash_save_vmcoreinfo support
>       https://git.kernel.org/palmer/c/649d6b1019a2

So this patch seems to be causing issues for the nommu build:
https://lore.kernel.org/oe-kbuild-all/202212062250.tR0otHcz-lkp@intel.com/

I had a bit of a poke at trying to see if there were some headers we
could pull in before actually checking the .config only to see:
# CONFIG_MMU is not set

Do we have to wrap the whole thing in a `#ifdef CONFIG_MMU` to fix
compilation here?

Thanks,
Conor.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2022-12-06 23:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 14:42 [PATCH V5 0/2] Support VMCOREINFO export for RISCV64 Xianting Tian
2022-10-26 14:42 ` [PATCH V5 1/2] RISC-V: Add arch_crash_save_vmcoreinfo support Xianting Tian
2022-11-17  4:15   ` Deepak Gupta
2022-11-17 15:43   ` Guo Ren
2022-10-26 14:42 ` [PATCH V5 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64 Xianting Tian
2022-10-31  9:17 ` [PATCH V5 0/2] Support " Baoquan He
2022-11-18  0:11 ` Baoquan He
2022-12-03  0:49 ` Palmer Dabbelt
2022-12-03  7:53   ` Guo Ren
2022-12-06 23:05   ` Conor Dooley [this message]
2022-12-07  3:34     ` Guo Ren
2022-12-07  8:08       ` Conor Dooley
2022-12-07  9:15         ` Guo Ren
2022-12-03  1:00 ` patchwork-bot+linux-riscv

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=Y4/KoiFhdvRBDdzH@spud \
    --to=conor@kernel.org \
    --cc=alexandre.ghiti@canonical.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bagasdotme@gmail.com \
    --cc=bhe@redhat.com \
    --cc=conor.dooley@microchip.com \
    --cc=corbet@lwn.net \
    --cc=crash-utility@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=guoren@kernel.org \
    --cc=heiko@sntech.de \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=hschauhan@nulltrace.org \
    --cc=k-hagio-ab@nec.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=vgoyal@redhat.com \
    --cc=xianting.tian@linux.alibaba.com \
    --cc=yixun.lan@gmail.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;
as well as URLs for NNTP newsgroup(s).