From: Michael Ellerman <mpe@ellerman.id.au>
To: Balbir Singh <bsingharora@gmail.com>, linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>,
aneesh.kumar@linux.vnet.ibm.com, linux-mm@kvack.org
Subject: Re: [PATCH] powerpc/mm: Always use STRICT_MM_TYPECHECKS
Date: Thu, 21 Apr 2016 16:36:02 +1000 [thread overview]
Message-ID: <1461220562.3245.3.camel@ellerman.id.au> (raw)
In-Reply-To: <571853FA.5080901@gmail.com>
On Thu, 2016-04-21 at 14:15 +1000, Balbir Singh wrote:
>
> On 21/04/16 13:37, Michael Ellerman wrote:
> > Testing done by Paul Mackerras has shown that with a modern compiler
> > there is no negative effect on code generation from enabling
> > STRICT_MM_TYPECHECKS.
> >
> > So remove the option, and always use the strict type definitions.
> >
>
> Should we wait for Aneesh's patches before merging this in.
Preferably not.
I've already rebased his patches on top of this, it's trivial, it's just
removing code.
It also makes some things we might want to do as part of his series easier
(like adding a raw accessor to get the __be64 pmd/pte val).
cheers
next prev parent reply other threads:[~2016-04-21 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 3:37 [PATCH] powerpc/mm: Always use STRICT_MM_TYPECHECKS Michael Ellerman
2016-04-21 4:15 ` Balbir Singh
2016-04-21 6:36 ` Michael Ellerman [this message]
2016-04-21 9:56 ` Arnd Bergmann
2016-04-28 5:27 ` Michael Ellerman
2016-04-28 5:13 ` Paul Mackerras
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=1461220562.3245.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).