mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Amelie Delaunay <amelie.delaunay@st.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] RTC support on STM32H743
Date: Tue, 27 Feb 2018 17:10:26 +0100	[thread overview]
Message-ID: <d53b5d88-1efa-36ca-e989-bad441d6cb96@st.com> (raw)
In-Reply-To: <1518787000-10675-1-git-send-email-amelie.delaunay@st.com>

Hi Amélie,

On 02/16/2018 02:16 PM, Amelie Delaunay wrote:
> This patchset add support for RTC on STM32H743 and enables it on stm32h743i-eval.
> Tested on stm32-next.
> 
> Amelie Delaunay (2):
>    ARM: dts: stm32: add RTC support on STM32H743
>    ARM: dts: stm32: enable RTC on stm32h743i-eval
> 
>   arch/arm/boot/dts/stm32h743.dtsi      | 15 +++++++++++++++
>   arch/arm/boot/dts/stm32h743i-eval.dts |  4 ++++
>   2 files changed, 19 insertions(+)
> 

Kbuild issue occurs on patch1 because MAINTAINER file is not correct for 
ARM/STM32. I send a patch to fix it: 
https://lkml.org/lkml/2018/2/26/386. There is no Kbuild issue if patches 
are applied on the correct branch: 
git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next.

So series applied on stm32-next.

regards
Alex

      parent reply	other threads:[~2018-02-27 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 13:16 Amelie Delaunay
2018-02-16 13:16 ` [PATCH 1/2] ARM: dts: stm32: add " Amelie Delaunay
2018-02-20  0:26   ` kbuild test robot
2018-02-16 13:16 ` [PATCH 2/2] ARM: dts: stm32: enable RTC on stm32h743i-eval Amelie Delaunay
2018-02-27 16:10 ` Alexandre Torgue [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=d53b5d88-1efa-36ca-e989-bad441d6cb96@st.com \
    --to=alexandre.torgue@st.com \
    --cc=amelie.delaunay@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh+dt@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
all inboxes | Powered by JetHome®