From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STM32 DT changes for v4.11 #1 V2
Date: Mon, 30 Jan 2017 21:04:35 -0800 [thread overview]
Message-ID: <20170131050435.GA16560@localhost> (raw)
In-Reply-To: <a8f6b0aa-412e-65b7-5d88-e4b17097c3a8@st.com>
On Fri, Jan 20, 2017 at 03:40:41PM +0100, Alexandre Torgue wrote:
> Hi Olof, Arnd and Kevin,
>
> Please consider this second version of first round of STM32 DT updates for
> v4.11:
>
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
>
> Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git
> tags/stm32-dt-for-v4.11-1-v2
>
> for you to fetch changes up to a4e6964a78946bf3ce969d9fef5f201e0236f0ea:
>
> ARM: dts: stm32: enable RTC on stm32429i-eval (2017-01-20 14:59:58 +0100)
>
> ----------------------------------------------------------------
> STM32 DT updates for v4.11, round 1 Version 2.
>
> Highlights:
> ----------
>
> - ADD RTC support on STM32F429 MCU
> - Enable RTC on STM32F469and STM32F429 boards
> - ADD ADC support on STM32F429 MCU
> - Enable ADC on STM32F429 Eval board
> - Add I2S external clock
> - Fix memory size for STM32F429 Disco
>
> Note:
> -----
> First patch "clk: stm32f4: Update DT bindings documentation")
> has already been merged in clock tree. Compare to version 1
> git merge has been used to take this patch.
Merged, thanks! Sorry for this taking a while.
Oh, minor comment: For next time, the note doesn't have to go in the tag
description, just the pull request.
-Olof
next prev parent reply other threads:[~2017-01-31 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 14:40 [GIT PULL] STM32 DT changes for v4.11 #1 V2 Alexandre Torgue
2017-01-30 5:33 ` Olof Johansson
2017-01-30 18:39 ` Stephen Boyd
2017-01-31 5:04 ` Olof Johansson [this message]
2017-01-31 8:16 ` Alexandre Torgue
2017-01-31 22:25 ` Olof Johansson
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=20170131050435.GA16560@localhost \
--to=olof@lixom.net \
--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).