From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Borntraeger <borntraeger@de•ibm.com>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
linuxppc-dev@lists•ozlabs.org,
Michael Ellerman <mpe@ellerman•id.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux•vnet.ibm.com>
Subject: linux-next: build failure after merge of the access_once tree
Date: Mon, 8 Dec 2014 22:26:41 +1100 [thread overview]
Message-ID: <20141208222641.40a64946@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hi Christian,
After merging the acess_once tree, today's linux-next build (powerpc
allnoconfig) failed like this:
arch/powerpc/mm/hugetlbpage.c: In function 'find_linux_pte_or_hugepte':
arch/powerpc/mm/hugetlbpage.c:981:3: error: invalid initializer
pud = ACCESS_ONCE(*pudp);
^
arch/powerpc/mm/hugetlbpage.c:993:4: error: invalid initializer
pmd = ACCESS_ONCE(*pmdp);
^
These are preexisting ...
mm/gup.c: In function 'gup_pmd_range':
mm/gup.c:929:3: error: invalid initializer
pmd_t pmd = ACCESS_ONCE(*pmdp);
^
mm/gup.c:929:3: error: (near initialization for 'pmd')
This is from commit f30c59e921f1 ("mm: Update generic gup
implementation to handle hugepage directory") from the powerpc-mpe (and
powerpc) tree and so will require a merge fix patch (presumable
s/ACCESS_ONCE/READ_ONCE/).
I am not sure how many architectures you are trying to cover, but
powerpc is one I care about :-)
I have dropped the access_once tree again today, sorry (its too late at
night).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-12-08 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 11:26 Stephen Rothwell [this message]
2014-12-08 11:35 ` linux-next: build failure after merge of the access_once tree Christian Borntraeger
2014-12-09 19:54 ` Christian Borntraeger
-- strict thread matches above, loose matches on Subject: below --
2014-12-10 8:20 Stephen Rothwell
2014-12-10 11:20 ` Christian Borntraeger
2014-12-05 10:32 Stephen Rothwell
2014-12-07 20:57 ` Christian Borntraeger
2014-12-07 21:16 ` Christian Borntraeger
2014-12-07 23:55 ` Stephen Rothwell
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=20141208222641.40a64946@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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