Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] STM32: Fixes for 4.19 cycle
Date: Tue, 25 Sep 2018 20:40:55 -0700	[thread overview]
Message-ID: <20180926034055.yj3re5o4oesda4x5@localhost> (raw)
In-Reply-To: <0f424a8e-67e0-cdc2-0276-660e455e3df6@st.com>

On Mon, Sep 24, 2018 at 11:28:17AM +0200, Alexandre Torgue wrote:
> Olof
> 
> On 09/24/2018 11:19 AM, Olof Johansson wrote:
> > Hi,
> > 
> > 
> > On Mon, Sep 24, 2018 at 7:55 AM, Alexandre Torgue
> > <alexandre.torgue@st.com> wrote:
> > > Hi Olof
> > > 
> > > On 09/23/2018 02:34 PM, Olof Johansson wrote:
> > > > 
> > > > Hi Alexandre,
> > > > 
> > > > On Thu, Sep 20, 2018 at 06:34:15PM +0200, Alexandre Torgue wrote:
> > > > > 
> > > > > Hi Arnd, olof and Kevin
> > > > > 
> > > > > Those 2 patches fixe the same issue on 4.19-rc: a bad usage of the mdma
> > > > > binding inside stm32mp157c.dts file. Can you please add them as fixe for
> > > > > 4.19 ?
> > > > 
> > > > 
> > > > The patches only mention removing unused property contents, not what the
> > > > bug is
> > > > that it fixes (or if it's even causing any problems). Care you clarify?
> > > 
> > > 
> > > Sure.
> > > Concerning SPI patch: without this patch, DMA request will fail but there
> > > will be no crash because SPI will switch in interrupt mode.
> > > Concerning HASH one, it's just to align DT with dt-bindings documentation.
> > > Regarding the minor issue that they fix I could understand that you postpone
> > > the merge of those two patches for 4.20.
> > 
> > The former sounds like an appropriate fix, but the latter is probably
> > 4.20 material, indeed.
> > 
> > Should I just cherry-pick the two patches, or do you want to re-stage
> > new branches?
> 
> I have nothing else to send for v4.20 so if you can directly take those two
> patches for v4.20, I agree.

Thanks! Applied to fixes and next/dt respectively.


-Olof

  reply	other threads:[~2018-09-26  3:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 16:34 [PATCH 0/2] STM32: Fixes for 4.19 cycle Alexandre Torgue
2018-09-20 16:34 ` [PATCH 1/2] ARM: dts: stm32: update SPI6 dmas property on stm32mp157c Alexandre Torgue
2018-09-20 16:34 ` [PATCH 2/2] ARM: dts: stm32: update HASH1 " Alexandre Torgue
2018-09-23 12:34 ` [PATCH 0/2] STM32: Fixes for 4.19 cycle Olof Johansson
2018-09-24  6:55   ` Alexandre Torgue
2018-09-24  9:19     ` Olof Johansson
2018-09-24  9:28       ` Alexandre Torgue
2018-09-26  3:40         ` Olof Johansson [this message]
2018-11-02 18:41           ` 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=20180926034055.yj3re5o4oesda4x5@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