From: mcoquelin.stm32@gmail.com (Maxime Coquelin)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STM32 SoC updates for v4.6 #2
Date: Wed, 2 Mar 2016 11:52:54 +0100 [thread overview]
Message-ID: <56D6C606.7070107@gmail.com> (raw)
Hi Olof, Arnd and Kevin,
Please consider this second round of STM32 SoC updates for v4.6:
The following changes since commit f64e980450027e15dce5e9ec4ee19bab98aee4c5:
ARM: mach-stm32: Select pinctrl (2016-01-27 19:45:57 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mcoquelin/stm32.git
tags/stm32-soc-for-v4.6-2
for you to fetch changes up to 6391503bbf4508ca97e9806b5347d3fd5d3c8c3c:
ARM: stm32: Identify a new SoC - STM32F469 (2016-02-17 17:30:44 +0100)
----------------------------------------------------------------
Highlights:
-----------
- Add a new stm32f469 SoC
----------------------------------------------------------------
Lee Jones (1):
ARM: stm32: Identify a new SoC - STM32F469
arch/arm/mach-stm32/board-dt.c | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2016-03-02 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 10:52 Maxime Coquelin [this message]
2016-03-02 22:38 ` [GIT PULL] STM32 SoC updates for v4.6 #2 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=56D6C606.7070107@gmail.com \
--to=mcoquelin.stm32@gmail.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