From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 7600/8035] arch/alpha/include/asm/page.h:21:64: error: 'vmaddr' undeclared
Date: Tue, 3 May 2022 00:22:26 +0100 [thread overview]
Message-ID: <YnBnsgjpttwC+Ds8@casper.infradead.org> (raw)
In-Reply-To: <202205022324.ypi9GtUO-lkp@intel.com>
On Mon, May 02, 2022 at 11:40:39PM +0800, kernel test robot wrote:
> commit: c4199a5358c9d22d9b88e2e6e4e94a8943415595 [7600/8035] mm: remove alloc_pages_vma()
> config: alpha-defconfig (https://download.01.org/0day-ci/archive/20220502/202205022324.ypi9GtUO-lkp@intel.com/config)
> mm/memory.c: In function 'wp_page_copy':
> >> arch/alpha/include/asm/page.h:21:64: error: 'vmaddr' undeclared (first use in this function)
> 21 | alloc_page_vma(GFP_HIGHUSER_MOVABLE | __GFP_ZERO, vma, vmaddr)
Oh, that's hilarious. This should be the fix:
diff --git a/arch/alpha/include/asm/page.h b/arch/alpha/include/asm/page.h
index 18f48a6f2ff6..8f3f5eecba28 100644
--- a/arch/alpha/include/asm/page.h
+++ b/arch/alpha/include/asm/page.h
@@ -18,7 +18,7 @@ extern void clear_page(void *page);
#define clear_user_page(page, vaddr, pg) clear_page(page)
#define alloc_zeroed_user_highpage_movable(vma, vaddr) \
- alloc_page_vma(GFP_HIGHUSER_MOVABLE | __GFP_ZERO, vma, vmaddr)
+ alloc_page_vma(GFP_HIGHUSER_MOVABLE | __GFP_ZERO, vma, vaddr)
#define __HAVE_ARCH_ALLOC_ZEROED_USER_HIGHPAGE_MOVABLE
extern void copy_page(void * _to, void * _from);
(whitespace damaged)
prev parent reply other threads:[~2022-05-02 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 15:40 [linux-next:master 7600/8035] arch/alpha/include/asm/page.h:21:64: error: 'vmaddr' undeclared kernel test robot
2022-05-02 23:22 ` Matthew Wilcox [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=YnBnsgjpttwC+Ds8@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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).