mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Bich HEMON <bich.hemon@st.com>,
	"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-stm32@st-md-mailman.stormreply.com" 
	<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 0/3] CAN fix for stm32mp157c
Date: Mon, 3 Dec 2018 09:58:07 +0100	[thread overview]
Message-ID: <ccc28b23-ce6d-41a9-74ea-2f7c85f69c84@st.com> (raw)
In-Reply-To: <1542271942-28130-1-git-send-email-bich.hemon@st.com>

Hi Bich,

On 11/15/18 9:52 AM, Bich HEMON wrote:
> This patchset changes the CAN RAM mapping and adds CAN sleep pins.
> 
> Bich Hemon (3):
>    ARM: dts: stm32: change CAN RAM mapping on stm32mp157c
>    ARM: dts: stm32: add can1 sleep pins muxing
>    ARM: dts: stm32: add can1 sleep pins muxing on stm32mp157c-ev1 board
> 
>   arch/arm/boot/dts/stm32mp157-pinctrl.dtsi | 7 +++++++
>   arch/arm/boot/dts/stm32mp157c-ev1.dts     | 3 ++-
>   arch/arm/boot/dts/stm32mp157c.dtsi        | 4 ++--
>   3 files changed, 11 insertions(+), 3 deletions(-)
> 
> -- 
> 1.9.1

Series applied on stm32-next.

Regards
Alex

      parent reply	other threads:[~2018-12-03  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  8:52 Bich HEMON
2018-11-15  8:52 ` [PATCH 3/3] ARM: dts: stm32: add can1 sleep pins muxing on stm32mp157c-ev1 board Bich HEMON
2018-11-15  8:52 ` [PATCH 2/3] ARM: dts: stm32: add can1 sleep pins muxing Bich HEMON
2018-11-15  8:52 ` [PATCH 1/3] ARM: dts: stm32: change CAN RAM mapping on stm32mp157c Bich HEMON
2018-12-03  8:58 ` 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=ccc28b23-ce6d-41a9-74ea-2f7c85f69c84@st.com \
    --to=alexandre.torgue@st.com \
    --cc=bich.hemon@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --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®