All of lore.kernel.org
 help / color / mirror / Atom feed
From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: NXP LPC32xx Defconfig Updates for v4.7
Date: Thu, 28 Apr 2016 03:11:40 +0300	[thread overview]
Message-ID: <5721553C.8050701@mleia.com> (raw)

Hi Arnd, Olof, Kevin,

please consider to include NXP LPC32xx defconfig updates for v4.7.

I'm adding an official LPC32xx maintainer Roland to Cc, however
he seems to be unresponsive for a quite long time.

Thank you in advance.


The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

  Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)

are available in the git repository at:

  git://github.com/vzapolskiy/linux-lpc32xx.git tags/lpc32xx-defconfig-4.7

for you to fetch changes up to 3b3c6ad5353951cd01523add5a1930c743d4f807:

  ARM: LPC32xx: add PL175 memory controller driver to defconfig (2016-04-21 22:25:26 +0300)

----------------------------------------------------------------
NXP LPC32xx defconfig updates for v4.7

This includes savedefconfig update of lpc32xx_defconfig, which removes
a number of outdated config options, plus ARM PrimeCell PL17x memory
controller driver is enabled by default now, on LPC32xx boards the
controller is commonly used to access SDRAM and NOR.

----------------------------------------------------------------
Vladimir Zapolskiy (2):
      ARM: LPC32xx: defconfig update
      ARM: LPC32xx: add PL175 memory controller driver to defconfig

 arch/arm/configs/lpc32xx_defconfig | 29 +++++++++++------------------
 1 file changed, 11 insertions(+), 18 deletions(-)

             reply	other threads:[~2016-04-28  0:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  0:11 Vladimir Zapolskiy [this message]
2016-04-28 15:49 ` NXP LPC32xx Defconfig Updates for v4.7 Arnd Bergmann

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=5721553C.8050701@mleia.com \
    --to=vz@mleia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.