From: Michael Ellerman <mpe@ellerman.id.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: aarcange@redhat.com, aneesh.kumar@in.ibm.com,
steve.capper@linaro.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
kirill.shutemov@linux.intel.com, Jason Low <jason.low2@hp.com>
Subject: Re: [PATCH 5/6] mm/gup: Replace ACCESS_ONCE with READ_ONCE for STRICT_MM_TYPECHECKS
Date: Wed, 25 Mar 2015 20:24:49 +1100 [thread overview]
Message-ID: <1427275489.31588.1.camel@ellerman.id.au> (raw)
In-Reply-To: <55127D65.7060605@de.ibm.com>
On Wed, 2015-03-25 at 10:18 +0100, Christian Borntraeger wrote:
> Am 25.03.2015 um 10:11 schrieb Michael Ellerman:
> > If STRICT_MM_TYPECHECKS is enabled the generic gup code fails to build
> > because we are using ACCESS_ONCE on non-scalar types.
> >
> > Convert all uses to READ_ONCE.
>
> There is a similar patch from Jason Low in Andrews patch.
Ah sorry, I didn't think to check.
> If that happens in 4.0-rc, we probably want to merge this before 4.0.
My series can wait, it's not urgent. So I'll plan to merge mine once Andrew's
tree has gone into Linus' tree for 4.1.
cheers
next prev parent reply other threads:[~2015-03-25 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 9:11 [PATCH 1/6] powerpc/mm: Remove duplicate declaration of setbat() Michael Ellerman
2015-03-25 9:11 ` [PATCH 2/6] powerpc/mm: Change setbat() to take a pgprot_t rather than flags Michael Ellerman
2015-03-25 9:11 ` [PATCH 3/6] powerpc: Make STRICT_MM_TYPECHECKS a config option Michael Ellerman
2015-03-25 9:11 ` [PATCH 4/6] powerpc: Fix compile errors with STRICT_MM_TYPECHECKS enabled Michael Ellerman
2015-03-25 9:11 ` [PATCH 5/6] mm/gup: Replace ACCESS_ONCE with READ_ONCE for STRICT_MM_TYPECHECKS Michael Ellerman
2015-03-25 9:18 ` Christian Borntraeger
2015-03-25 9:24 ` Michael Ellerman [this message]
2015-03-25 9:11 ` [RFC PATCH 6/6] powerpc: Always enable STRICT_MM_TYPECHECKS Michael Ellerman
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=1427275489.31588.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@in.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=jason.low2@hp.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=steve.capper@linaro.org \
--cc=torvalds@linux-foundation.org \
/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