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>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Simek <monstr@monstr.eu>
Subject: Re: linux-next: Tree for Nov 17 (microblaze + highmem changes)
Date: Tue, 17 Nov 2020 19:57:23 -0800 [thread overview]
Message-ID: <03628cc1-d08e-fada-a5ab-f1942d09a461@infradead.org> (raw)
In-Reply-To: <20201117184627.62a9b2f0@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 3667 bytes --]
On 11/16/20 11:46 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201116:
>
on arch/microblaze/, without CONFIG_HIGHMEM:
also CONFIG_MMU is not set.
Note this one also:
../arch/microblaze/mm/init.c: At top level:
../arch/microblaze/mm/init.c:71:2: error: #endif without #if
In file included from ../include/linux/kernel.h:16,
from ../include/linux/list.h:9,
from ../include/linux/rculist.h:10,
from ../include/linux/pid.h:5,
from ../include/linux/sched.h:14,
from ../include/linux/ratelimit.h:6,
from ../include/linux/dev_printk.h:16,
from ../include/linux/device.h:15,
from ../include/linux/dma-mapping.h:7,
from ../include/linux/dma-map-ops.h:9,
from ../arch/microblaze/mm/init.c:10:
../arch/microblaze/mm/init.c: In function 'highmem_init':
../arch/microblaze/mm/init.c:54:24: error: 'PKMAP_BASE' undeclared (first use in this function); did you mean 'AT_BASE'?
54 | pr_debug("%x\n", (u32)PKMAP_BASE);
| ^~~~~~~~~~
../include/linux/printk.h:140:17: note: in definition of macro 'no_printk'
140 | printk(fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
../arch/microblaze/mm/init.c:54:2: note: in expansion of macro 'pr_debug'
54 | pr_debug("%x\n", (u32)PKMAP_BASE);
| ^~~~~~~~
../arch/microblaze/mm/init.c:54:24: note: each undeclared identifier is reported only once for each function it appears in
54 | pr_debug("%x\n", (u32)PKMAP_BASE);
| ^~~~~~~~~~
../include/linux/printk.h:140:17: note: in definition of macro 'no_printk'
140 | printk(fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
../arch/microblaze/mm/init.c:54:2: note: in expansion of macro 'pr_debug'
54 | pr_debug("%x\n", (u32)PKMAP_BASE);
| ^~~~~~~~
EXTRACT_CERTS
../arch/microblaze/mm/init.c:55:2: error: implicit declaration of function 'map_page' [-Werror=implicit-function-declaration]
55 | map_page(PKMAP_BASE, 0, 0); /* XXX gross */
| ^~~~~~~~
CC certs/blacklist.o
../arch/microblaze/mm/init.c:56:2: error: 'pkmap_page_table' undeclared (first use in this function)
56 | pkmap_page_table = virt_to_kpte(PKMAP_BASE);
| ^~~~~~~~~~~~~~~~
../arch/microblaze/mm/init.c:56:21: error: implicit declaration of function 'virt_to_kpte'; did you mean 'virt_to_pfn'? [-Werror=implicit-function-declaration]
56 | pkmap_page_table = virt_to_kpte(PKMAP_BASE);
| ^~~~~~~~~~~~
| virt_to_pfn
../arch/microblaze/mm/init.c: In function 'highmem_setup':
../arch/microblaze/mm/init.c:68:4: error: implicit declaration of function 'free_highmem_page'; did you mean 'free_unref_page'? [-Werror=implicit-function-declaration]
68 | free_highmem_page(page);
| ^~~~~~~~~~~~~~~~~
| free_unref_page
../arch/microblaze/mm/init.c: At top level:
../arch/microblaze/mm/init.c:71:2: error: #endif without #if
71 | #endif /* CONFIG_HIGHMEM */
| ^~~~~
CC arch/microblaze/kernel/cpu/cpuinfo.o
../arch/microblaze/mm/init.c:59:13: warning: 'highmem_setup' defined but not used [-Wunused-function]
59 | static void highmem_setup(void)
| ^~~~~~~~~~~~~
../arch/microblaze/mm/init.c:52:20: warning: 'highmem_init' defined but not used [-Wunused-function]
52 | static void __init highmem_init(void)
| ^~~~~~~~~~~~
cc1: some warnings being treated as errors
Kernel config file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: ublz.config --]
[-- Type: application/x-config, Size: 161289 bytes --]
prev parent reply other threads:[~2020-11-18 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 7:46 linux-next: Tree for Nov 17 Stephen Rothwell
2020-11-18 3:57 ` Randy Dunlap [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=03628cc1-d08e-fada-a5ab-f1942d09a461@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).