From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Dec 23 (ia64: mmzone & sparsemem)
Date: Sat, 26 Dec 2020 18:25:56 -0800 [thread overview]
Message-ID: <4cea81fb-f8df-ec09-5591-1c8ca4f770d8@infradead.org> (raw)
In-Reply-To: <20201223154542.544915be@canb.auug.org.au>
On 12/22/20 8:45 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next releases between Dec 24 and Jan
> 3 inclusive.
>
> Please do not add any v5.12 destined code to your linux-next included
> branches until after v5.11-rc1 has been released.
>
> Changes since 20201222:
>
on ia64 defconfig:
several of these:
In file included from ../include/linux/numa.h:25,
from ../include/linux/nodemask.h:96,
from ../include/linux/mount.h:15,
from ../fs/nsfs.c:2:
../arch/ia64/include/asm/sparsemem.h:14:40: warning: "PAGE_SHIFT" is not defined, evaluates to 0 [-Wundef]
14 | #if ((CONFIG_FORCE_MAX_ZONEORDER - 1 + PAGE_SHIFT) > SECTION_SIZE_BITS)
and several of these:
In file included from ../include/linux/gfp.h:6,
from ../include/linux/xarray.h:14,
from ../include/linux/radix-tree.h:19,
from ../include/linux/idr.h:15,
from ../include/linux/kernfs.h:13,
from ../include/linux/sysfs.h:16,
from ../include/linux/kobject.h:20,
from ../include/linux/energy_model.h:7,
from ../include/linux/device.h:16,
from ../include/linux/async.h:14,
from ../kernel/async.c:47:
../include/linux/mmzone.h:1156:2: error: #error Allocator MAX_ORDER exceeds SECTION_SIZE
1156 | #error Allocator MAX_ORDER exceeds SECTION_SIZE
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
parent reply other threads:[~2020-12-27 2:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201223154542.544915be@canb.auug.org.au>]
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=4cea81fb-f8df-ec09-5591-1c8ca4f770d8@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.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).