All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.ozlabs.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the powerpc-mpe tree
Date: Sat, 11 Apr 2015 20:39:11 +1000	[thread overview]
Message-ID: <1428748751.1552.0.camel@ellerman.id.au> (raw)
In-Reply-To: <20150410200240.13471ce4@canb.auug.org.au>

On Fri, 2015-04-10 at 20:02 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the powerpc-mpe tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> mm/gup.c: In function 'gup_pte_range':
> mm/gup.c:904:3: error: conversion to non-scalar type requested
>    pte_t pte = ACCESS_ONCE(*ptep);
>    ^
> mm/gup.c: In function '__get_user_pages_fast':
> mm/gup.c:1194:3: error: conversion to non-scalar type requested
>    pgd_t pgd = ACCESS_ONCE(*pgdp);
>    ^
> 
> Caused by commit 4bcad5b3b3ea ("powerpc: Make STRICT_MM_TYPECHECKS a
> config option").
> 
> I have reverted that commit for today.

I've dropped it from my tree for now.

You can kill me on Monday.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the powerpc-mpe tree
Date: Sat, 11 Apr 2015 20:39:11 +1000	[thread overview]
Message-ID: <1428748751.1552.0.camel@ellerman.id.au> (raw)
In-Reply-To: <20150410200240.13471ce4@canb.auug.org.au>

On Fri, 2015-04-10 at 20:02 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the powerpc-mpe tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> mm/gup.c: In function 'gup_pte_range':
> mm/gup.c:904:3: error: conversion to non-scalar type requested
>    pte_t pte = ACCESS_ONCE(*ptep);
>    ^
> mm/gup.c: In function '__get_user_pages_fast':
> mm/gup.c:1194:3: error: conversion to non-scalar type requested
>    pgd_t pgd = ACCESS_ONCE(*pgdp);
>    ^
> 
> Caused by commit 4bcad5b3b3ea ("powerpc: Make STRICT_MM_TYPECHECKS a
> config option").
> 
> I have reverted that commit for today.

I've dropped it from my tree for now.

You can kill me on Monday.

cheers

  reply	other threads:[~2015-04-11 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 10:02 linux-next: build failure after merge of the powerpc-mpe tree Stephen Rothwell
2015-04-10 10:02 ` Stephen Rothwell
2015-04-11 10:39 ` Michael Ellerman [this message]
2015-04-11 10:39   ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2015-03-26  2:29 Stephen Rothwell
2015-03-26  2:29 ` Stephen Rothwell
2015-03-26  2:29 ` Stephen Rothwell
2015-03-26  2:35 ` Benjamin Herrenschmidt
2015-03-26  2:35   ` Benjamin Herrenschmidt

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=1428748751.1552.0.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.