From: stuart.yoder@nxp.com (Stuart Yoder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: defconfig updates
Date: Tue, 19 Apr 2016 17:39:00 -0500 [thread overview]
Message-ID: <1461105540-23799-1-git-send-email-stuart.yoder@nxp.com> (raw)
This patch series was based on 4.6-rc4.
As far as I know, when doing a 'make defconfig' immediately followed by
'make savedefconfig', the resulting defconfig should exactly match
the original defconfig. This was not the case for arm64 and patch 1 cleans
that up.
Patch 2 enables 48-bit VA to allow certain armv8 SoCs to cover all of
their physical memory regions. (see email thread:
http://www.spinics.net/lists/arm-kernel/msg497210.html)
Patch 3 enables some additional device for Freescale/NXP SoCs.
Stuart Yoder (3):
arm64: defconfig: cleanup the defconfig
arm64: defconfig: enable 48-bit virtual addresses
arm64: defconfig: enable freescale/nxp config options
arch/arm64/configs/defconfig | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
--
1.9.0
next reply other threads:[~2016-04-19 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 22:39 Stuart Yoder [this message]
2016-04-19 23:18 ` [PATCH 0/3] arm64: defconfig updates Arnd Bergmann
2016-04-20 9:12 ` Will Deacon
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=1461105540-23799-1-git-send-email-stuart.yoder@nxp.com \
--to=stuart.yoder@nxp.com \
--cc=linux-arm-kernel@lists.infradead.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).