linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>,
	linux-xtensa@linux-xtensa.org, ngupta@vflare.org,
	sergey.senozhatsky.work@gmail.com, sjenning@linux.vnet.ibm.com,
	gregkh@linuxfoundation.org, arnd@arndb.de,
	Stefan Agner <stefan@agner.ch>, Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH] mm: fix build failure with xtensa
Date: Tue, 10 Nov 2020 14:08:37 -0800	[thread overview]
Message-ID: <20201110140837.99b1feabec8754ce5247e2a0@linux-foundation.org> (raw)
In-Reply-To: <20201110220151.20911-1-sudipm.mukherjee@gmail.com>

On Tue, 10 Nov 2020 22:01:51 +0000 Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:

> If CONFIG_ZSMALLOC is enabled with xtensa then the build fails with:
> mm/zsmalloc.c:43:10: fatal error: asm/sparsemem.h: No such file or directory
> 
> Disable CONFIG_ZSMALLOC for xtensa as xtensa arch has not defined
> sparsemem.h.
> 
> ...
>
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -698,7 +698,7 @@ config Z3FOLD
>  
>  config ZSMALLOC
>  	tristate "Memory allocator for compressed pages"
> -	depends on MMU
> +	depends on (MMU && !XTENSA)
>  	help
>  	  zsmalloc is a slab-based memory allocator designed to store
>  	  compressed RAM pages.  zsmalloc uses virtual memory mapping

Thanks.  I believe that Stefan is working on a more general solution
over in
https://lkml.kernel.org/r/bdfa44bf1c570b05d6c70898e2bbb0acf234ecdf.1604762181.git.stefan@agner.ch



      reply	other threads:[~2020-11-10 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 22:01 Sudip Mukherjee
2020-11-10 22:08 ` Andrew Morton [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=20201110140837.99b1feabec8754ce5247e2a0@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=chris@zankel.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sjenning@linux.vnet.ibm.com \
    --cc=stefan@agner.ch \
    --cc=sudipm.mukherjee@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