From: David Rientjes <rientjes@google.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@01.org
Subject: Re: [next:master 77/159] fs/proc/task_mmu.c:505:193: error: call to '__compiletime_assert_505' declared with attribute error: BUILD_BUG failed
Date: Thu, 19 Jun 2014 01:33:56 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1406190133060.13670@chino.kir.corp.google.com> (raw)
In-Reply-To: <53a29abf.v2bhnSChDbNTCQGt%fengguang.wu@intel.com>
On Thu, 19 Jun 2014, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 07d0e2d232fee3ff692c50150b2aa6e3b7755f8f
> commit: b0e08c526179642dccfd2c7caff31d2419492829 [77/159] mm/pagewalk: move pmd_trans_huge_lock() from callbacks to common code
> config: make ARCH=i386 defconfig
>
> Note: the next/master HEAD 07d0e2d232fee3ff692c50150b2aa6e3b7755f8f builds fine.
> It only hurts bisectibility.
>
> All error/warnings:
>
> fs/proc/task_mmu.c: In function 'smaps_pmd':
> >> fs/proc/task_mmu.c:505:193: error: call to '__compiletime_assert_505' declared with attribute error: BUILD_BUG failed
> smaps_pte((pte_t *)pmd, addr, addr + HPAGE_PMD_SIZE, walk);
> ^
> >> fs/proc/task_mmu.c:506:178: error: call to '__compiletime_assert_506' declared with attribute error: BUILD_BUG failed
> mss->anonymous_thp += HPAGE_PMD_SIZE;
> ^
mm-pagewalk-move-pmd_trans_huge_lock-from-callbacks-to-common-code.patch
was removed from -mm on Monday. We probably need to wait for another
mmotm before this vanishes.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-06-19 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 8:09 kbuild test robot
2014-06-19 8:33 ` David Rientjes [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=alpine.DEB.2.02.1406190133060.13670@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.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