From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
Michael Ellerman <mpe@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Darren Stevens <darren@stevens-zone.net>,
linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <michaele@au1.ibm.com>,
Julian Margetson <runaway@candw.ms>,
Adrian Cox <adrian@humboldt.co.uk>,
"R.T.Dickinson" <rtd@a-eon.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>, Pat Wall <pjwall@mac.com>,
Pat Wall <pjwall@me.com>, "contact@a-eon.com" <contact@a-eon.com>,
Matthew Leaman <matthew@a-eon.biz>,
luigi burdo <intermediadc@hotmail.com>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE
Date: Mon, 13 Jun 2016 18:19:27 +1000 [thread overview]
Message-ID: <1465805967.3022.14.camel@kernel.crashing.org> (raw)
In-Reply-To: <25BBCC66-53B2-4009-B2BA-CD1070EA71E9@xenosoft.de>
On Mon, 2016-06-13 at 09:14 +0100, Christian Zigotzky wrote:
> Can I disable the new PowerPC features with
>
> Radix MMU Support (PPC_RADIX_MMU) [Y/n/?] (NEW) -> n
>
> ?????
>
> I can't compile the RC3 without the PowerPC commits. Our kernel lost
> the mainline kernel support. Revert of the three PowerPC commits
> works but the kernel doesn't compile anymore.
The right way to not have this problem anymore is to cleanup and
submit your patches upstream so they don't break all the time :-)
Cheers,
Ben.
next prev parent reply other threads:[~2016-06-13 8:20 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 4:38 PAGE_GUARDED Christian Zigotzky
2016-05-23 8:01 ` PAGE_GUARDED Benjamin Herrenschmidt
2016-05-24 10:48 ` PAGE_GUARDED Christian Zigotzky
2016-05-24 11:16 ` PAGE_GUARDED Benjamin Herrenschmidt
2016-05-24 13:37 ` PAGE_GUARDED Christian Zigotzky
2016-05-24 15:37 ` PAGE_GUARDED Aneesh Kumar K.V
2016-05-25 6:58 ` PAGE_GUARDED Christian Zigotzky
2016-05-25 11:44 ` PAGE_GUARDED Christian Zigotzky
2016-06-04 7:19 ` Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE Christian Zigotzky
2016-06-04 7:40 ` Christian Zigotzky
2016-06-04 11:08 ` Christian Zigotzky
2016-06-04 14:46 ` Aneesh Kumar K.V
2016-06-04 15:13 ` Christian Zigotzky
2016-06-04 15:25 ` Christian Zigotzky
2016-06-05 16:09 ` Christian Zigotzky
2016-06-06 0:57 ` Michael Ellerman
2016-06-06 1:23 ` Julian Margetson
2016-06-06 2:00 ` Michael Ellerman
2016-06-06 8:59 ` Julian Margetson
2016-06-06 0:54 ` Michael Ellerman
2016-06-04 14:42 ` Aneesh Kumar K.V
2016-06-04 15:07 ` Christian Zigotzky
2016-06-06 0:51 ` Michael Ellerman
2016-06-06 5:21 ` Christian Zigotzky
2016-06-07 20:17 ` Christian Zigotzky
2016-06-07 22:14 ` Christian Zigotzky
2016-06-08 1:51 ` Michael Ellerman
2016-06-08 2:52 ` Michael Ellerman
2016-06-08 10:58 ` Christian Zigotzky
2016-06-08 11:30 ` Michael Ellerman
2016-06-08 12:50 ` Christian Zigotzky
2016-06-08 11:33 ` Darren Stevens
2016-06-08 13:24 ` Christian Zigotzky
2016-06-08 13:51 ` Christian Zigotzky
2016-06-08 13:52 ` Michael Ellerman
2016-06-08 15:11 ` Aneesh Kumar K.V
2016-06-08 15:47 ` Christian Zigotzky
2016-06-09 8:48 ` Christian Zigotzky
2016-06-09 11:15 ` Michael Ellerman
2016-06-09 13:13 ` Christian Zigotzky
2016-06-13 8:14 ` Christian Zigotzky
2016-06-13 8:19 ` Benjamin Herrenschmidt [this message]
2016-06-13 18:09 ` Christian Zigotzky
2016-06-22 19:07 ` Christian Zigotzky
2016-06-22 19:58 ` luigi burdo
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=1465805967.3022.14.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=adrian@humboldt.co.uk \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=chzigotzky@xenosoft.de \
--cc=contact@a-eon.com \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=intermediadc@hotmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew@a-eon.biz \
--cc=michaele@au1.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=pjwall@mac.com \
--cc=pjwall@me.com \
--cc=rtd2@xtra.co.nz \
--cc=rtd@a-eon.com \
--cc=runaway@candw.ms \
/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).