From: Kevin Hao <haokexin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Scott Wood <scottwood@freescale.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: [PATCH v2 0/3] powerpc: tweak the kernel options for CRASH_DUMP and RELOCATABLE
Date: Wed, 13 Jul 2016 09:14:37 +0800 [thread overview]
Message-ID: <1468372480-6453-1-git-send-email-haokexin@gmail.com> (raw)
v2:
Compare to v1 [1], the main differences are:
- Still automatically select RELOCATABLE when CRASH_DUMP is enabled.
- Add a new patch to kill RELOCATABLE_PPC32.
v1:
The first patch fixes a build error when CRASH_DUMP=y && ADVANCED_OPTIONS=n
for ppc32. The second does some cleanup for RELOCATABLE option.
Kevin Hao (3):
powerpc32: booke: fix the build error when CRASH_DUMP is enabled
powerpc: merge the RELOCATABLE config entries for ppc32 and ppc64
powerpc32: kill RELOCATABLE_PPC32
arch/powerpc/Kconfig | 61 +++++++++++++++------------------------
arch/powerpc/include/asm/page.h | 6 ++--
arch/powerpc/kernel/Makefile | 3 +-
arch/powerpc/kernel/vmlinux.lds.S | 2 +-
arch/powerpc/mm/init_32.c | 2 +-
5 files changed, 29 insertions(+), 45 deletions(-)
[1] http://linuxppc-dev.ozlabs.narkive.com/fKHcSZbu/patch-0-2-powerpc-tweak-the-kernel-options-for-crash-dump-and-relocatable
--
2.8.1
next reply other threads:[~2016-07-13 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 1:14 Kevin Hao [this message]
2016-07-13 1:14 ` [PATCH v2 1/3] powerpc32: booke: fix the build error when CRASH_DUMP is enabled Kevin Hao
2016-07-20 9:10 ` [v2, " Michael Ellerman
2016-07-13 1:14 ` [PATCH v2 2/3] powerpc: merge the RELOCATABLE config entries for ppc32 and ppc64 Kevin Hao
2016-07-13 1:14 ` [PATCH v2 3/3] powerpc32: kill RELOCATABLE_PPC32 Kevin Hao
-- strict thread matches above, loose matches on Subject: below --
2016-07-13 1:12 [PATCH v2 0/3] powerpc: tweak the kernel options for CRASH_DUMP and RELOCATABLE Kevin Hao
2016-07-13 1:16 ` Kevin Hao
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=1468372480-6453-1-git-send-email-haokexin@gmail.com \
--to=haokexin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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).