From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: update STM32 maintainers list
Date: Tue, 05 Jul 2016 16:01:14 +0200 [thread overview]
Message-ID: <3305022.xJDcuaUJlj@wuerfel> (raw)
In-Reply-To: <5774EAC0.4080906@st.com>
On Thursday, June 30, 2016 11:47:44 AM CEST Alexandre Torgue wrote:
>
> On 06/22/2016 03:56 PM, Maxime Coquelin wrote:
> > I will have less time to work on STM32 platform, so I propose
> > Alexandre as co-maintainer.
> >
> > Alex is working in the STMicroelectronics division in charge of STM32
> > family, so he will have access to all technical information and
> > hardware.
> >
> > Signed-off-by: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> > Cc: Alexandre Torgue <alexandre.torgue@st.com>
> Acked-by: Alexandre Torgue <alexandre.torgue@st.com>
I've decided to apply this directly to the fixes branch for 4.7, thanks!
Arnd
prev parent reply other threads:[~2016-07-05 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 13:56 [PATCH] MAINTAINERS: update STM32 maintainers list Maxime Coquelin
2016-06-30 9:47 ` Alexandre Torgue
2016-07-05 14:01 ` Arnd Bergmann [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=3305022.xJDcuaUJlj@wuerfel \
--to=arnd@arndb.de \
--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