From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kars de Jong <karsdejong@home.nl>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: m68k Kconfig warning
Date: Mon, 2 Dec 2019 14:32:28 +0100 [thread overview]
Message-ID: <CAMuHMdW1iqNkmCztAv93W4eLR5ooxh5m+vRLJHJmCfrjsOmc5g@mail.gmail.com> (raw)
In-Reply-To: <CACz-3rjOPg_rMt_FbJ5_nKLpjTK-Bv=amGsJpXwqbTBNX4YA7w@mail.gmail.com>
Hi Kars,.
On Mon, Dec 2, 2019 at 12:42 PM Kars de Jong <karsdejong@home.nl> wrote:
> Op wo 27 nov. 2019 om 08:12 schreef Geert Uytterhoeven <geert@linux-m68k.org>:
> > On Wed, Nov 27, 2019 at 2:27 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> > > Just noticed this. I don't know what the right fix is.
> > > Would you take care of it, please?
> > >
> > > on Linux 5.4, m68k allmodconfig:
> > >
> > > WARNING: unmet direct dependencies detected for NEED_MULTIPLE_NODES
> > > Depends on [n]: DISCONTIGMEM [=n] || NUMA
> > > Selected by [y]:
> > > - SINGLE_MEMORY_CHUNK [=y] && MMU [=y]
> >
> > This has been basically there forever, but working.
>
> The reason for SINGLE_MEMORY_CHUNK depending on NEED_MULTIPLE_NODES is
> historic due to the way it is implemented.
> I played with it this weekend and I got a working version of FLATMEM,
> which can replace SINGLE_MEMORY_CHUNK.
Nice, thanks!
> step might be to replace DISCONTIGMEM with SPARSEMEM (since
> DISCONTIGMEM has been deprecated).
Mike Rapoport has patches for that:
"[PATCH v2 0/3] m68k/mm: switch from DISCONTIGMEM to SPARSEMEM"
Unfortunately they're not on lore, and there were some issues with them.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-12-02 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 1:27 m68k Kconfig warning Randy Dunlap
2019-11-27 7:12 ` Geert Uytterhoeven
2019-12-02 11:42 ` Kars de Jong
2019-12-02 13:32 ` Geert Uytterhoeven [this message]
2019-12-02 16:01 ` Mike Rapoport
2019-12-04 11:58 ` Kars de Jong
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=CAMuHMdW1iqNkmCztAv93W4eLR5ooxh5m+vRLJHJmCfrjsOmc5g@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=karsdejong@home.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rdunlap@infradead.org \
--cc=rppt@linux.ibm.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).