public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STM32 defconfig changes for v4.19 #1
Date: Fri, 13 Jul 2018 16:01:40 +0200	[thread overview]
Message-ID: <016b1449-4ede-9302-e6f9-c52b63e0330e@st.com> (raw)

Hi Arnd, Olof and Kevin,

Please consider this first round of STM32 defconfig updates for v4.19.
This time it concerns only multi_v7_defconfig.

Thanks.
Alex

The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:

   Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)

are available in the git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git 
tags/stm32-defconfig-for-v4.19-1

for you to fetch changes up to 1b8a8589a3e10997fa8f43e7da874c4903f33ac7:

   ARM: multi_v7_defconfig: enable STM32 DCMI media support (2018-07-13 
14:54:24 +0200)

----------------------------------------------------------------
STM32 defconfig updates for v4.19, round 1

Highlights:
----------

In multi_v7_defconfig, add support of:

-STM32 RTC
-STM32 DMA, DMAMUX and MDMA
-STM32 DCMI media

----------------------------------------------------------------
Amelie Delaunay (1):
       ARM: multi_v7_defconfig: enable STM32 RTC

Hugues Fruchet (1):
       ARM: multi_v7_defconfig: enable STM32 DCMI media support

Pierre-Yves MORDRET (1):
       ARM: multi_v7_defconfig: enable STM32 DMAv2, DMAMUX and MDMA

  arch/arm/configs/multi_v7_defconfig | 5 +++++
  1 file changed, 5 insertions(+)

             reply	other threads:[~2018-07-13 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 14:01 Alexandre Torgue [this message]
2018-07-14 21:31 ` [GIT PULL] STM32 defconfig changes for v4.19 #1 Olof Johansson
2018-07-16 11:55   ` Alexandre Torgue

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=016b1449-4ede-9302-e6f9-c52b63e0330e@st.com \
    --to=alexandre.torgue@st.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