From: Maxime Coquelin <mcoquelin.stm32@gmail.com>
To: Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: kernel@stlinux.com, arnd@arndb.de
Subject: Re: [PATCH 0/3] ARM: stm32: Introduce support for STM32F469
Date: Thu, 18 Feb 2016 09:19:47 +0100 [thread overview]
Message-ID: <56C57EA3.4030506@gmail.com> (raw)
In-Reply-To: <1455632221-31834-1-git-send-email-lee.jones@linaro.org>
Hi Lee,
On 02/16/2016 03:16 PM, Lee Jones wrote:
> Simple set using the STM32F429 infrastructure as a foundation.
> There will be more changes to the DTS files and a requirement for
> added hierarchical layering as more differences become apparent.
>
> Lee Jones (3):
> ARM: stm32: Supply a DTS file for the STM32F469 Discovery board
> ARM: configs: Add new config fragment to change RAM start point
> ARM: stm32: Identify a new board - STM32F469
>
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/stm32f469-disco.dts | 75 +++++++++++++++++++++++++++++++++
> arch/arm/configs/dram_0x00000000.config | 1 +
> arch/arm/mach-stm32/board-dt.c | 1 +
> 4 files changed, 78 insertions(+)
> create mode 100644 arch/arm/boot/dts/stm32f469-disco.dts
> create mode 100644 arch/arm/configs/dram_0x00000000.config
>
Series applied to my tree for v4.6.
Thanks!
Maxime
prev parent reply other threads:[~2016-02-18 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:16 [PATCH 0/3] ARM: stm32: Introduce support for STM32F469 Lee Jones
2016-02-16 14:16 ` [PATCH 1/3] ARM: stm32: Supply a DTS file for the STM32F469 Discovery board Lee Jones
2016-02-16 14:17 ` [PATCH 2/3] ARM: configs: Add new config fragment to change RAM start point Lee Jones
2016-02-16 14:17 ` [PATCH 3/3] ARM: stm32: Identify a new board - STM32F469 Lee Jones
2016-02-16 14:36 ` [PATCH 0/3] ARM: stm32: Introduce support for STM32F469 Arnd Bergmann
2016-02-18 8:19 ` Maxime Coquelin [this message]
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=56C57EA3.4030506@gmail.com \
--to=mcoquelin.stm32@gmail.com \
--cc=arnd@arndb.de \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).