public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Baoquan He <bhe@redhat•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	linux-riscv <linux-riscv@lists•infradead.org>,
	kexec <kexec@lists•infradead.org>
Subject: Re: linux-next: Tree for Dec 1 (riscv, crash_core)
Date: Fri, 1 Dec 2023 20:55:08 -0800	[thread overview]
Message-ID: <a2295a13-3306-4522-913c-acdcd5eed950@infradead.org> (raw)
In-Reply-To: <ZWqU1+Xxr6PG+2Ov@MiWiFi-R3L-srv>

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



On 12/1/23 18:22, Baoquan He wrote:
> On 12/01/23 at 11:53am, Randy Dunlap wrote:
>>
>>
>> On 11/30/23 18:37, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20231130:
>>>
>>
>> on riscv 32-bit or 64-bit, with
>> # CONFIG_MMU is not set
> 
> Can you provide your .config so that I reproduce it? Disabling
> CONFIG_MMU need find all places where it's selected by other config items.
> 

Sure. This is for riscv 64-bit.

-- 
~Randy

[-- Attachment #2: config-r3049.gz --]
[-- Type: application/gzip, Size: 39057 bytes --]

  reply	other threads:[~2023-12-02  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  2:37 linux-next: Tree for Dec 1 Stephen Rothwell
2023-12-01 19:53 ` linux-next: Tree for Dec 1 (riscv, crash_core) Randy Dunlap
2023-12-02  2:22   ` Baoquan He
2023-12-02  4:55     ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-04  2:10 Baoquan He
2023-12-04 19:11 ` Randy Dunlap

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=a2295a13-3306-4522-913c-acdcd5eed950@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=bhe@redhat$(echo .)com \
    --cc=kexec@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-riscv@lists$(echo .)infradead.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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