public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: defconfig updates
Date: Wed, 20 Apr 2016 01:18:28 +0200	[thread overview]
Message-ID: <7790483.f4tRIAaceA@wuerfel> (raw)
In-Reply-To: <1461105540-23799-1-git-send-email-stuart.yoder@nxp.com>

On Tuesday 19 April 2016 17:39:00 Stuart Yoder wrote:
> 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.
> 

The series looks fine to me. I'd suggest merging it through the
platform maintainer path, e.g. having the i.MX mainainers pick
them up and forward them to arm at kernel.org for inclusion in arm-soc.

If the arm64 maintainers want to pick them up (or maybe just patches
1 and 2, which are not platform specific), that's fine too, and you
can add my

Acked-by: Arnd Bergmann <arnd@arndb.de>

We haven't come up with a really good way to deal with this kind of
update for arm64, as a lot of the changes to the defconfig file are
related to stuff that goes through arm-soc, but some other stuff
doesn't.

	Arnd

  reply	other threads:[~2016-04-19 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 22:39 [PATCH 0/3] arm64: defconfig updates Stuart Yoder
2016-04-19 23:18 ` Arnd Bergmann [this message]
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=7790483.f4tRIAaceA@wuerfel \
    --to=arnd@arndb.de \
    --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