From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: Ohad Ben Cohen <ohad@wizery.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v4 0/4] Add support of STM32 hwspinlock
Date: Wed, 5 Dec 2018 17:10:45 -0800 [thread overview]
Message-ID: <20181206011045.GA23336@builder> (raw)
In-Reply-To: <CA+M3ks5m1=gsGqB55T4xSGtAQW9Ct3Fxqx-gbYg=GoNwoX6B-w@mail.gmail.com>
On Fri 30 Nov 06:45 PST 2018, Benjamin Gaignard wrote:
> Le mer. 14 nov. 2018 à 10:00, Benjamin Gaignard
> <benjamin.gaignard@linaro.org> a écrit :
> >
> > This serie adds the support of the hardware semaphore block for stm32mp1 SoC.
> >
> > version 4:
> > - add Linaro SoB
>
> Gentle ping on this series
>
Sorry about that Benjamin, I was convinced that I picked your patches
already. Applied first two patches to hwspinlock tree.
I expect the dts update to go through the ST tree, and I guess the
complaint from 0day tells us they already are?
Regards,
Bjorn
next prev parent reply other threads:[~2018-12-06 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 9:00 [PATCH v4 0/4] Add support of STM32 hwspinlock Benjamin Gaignard
2018-11-14 9:00 ` [PATCH v4 1/4] dt-bindings: hwlock: Document STM32 hwspinlock bindings Benjamin Gaignard
2018-11-14 9:00 ` [PATCH v4 2/4] hwspinlock: add STM32 hwspinlock device Benjamin Gaignard
2018-11-14 9:00 ` [PATCH v4 3/4] ARM: dts: stm32: Add hwspinlock node for stm32mp157 SoC Benjamin Gaignard
2018-11-16 15:24 ` kbuild test robot
2018-12-06 9:59 ` Benjamin Gaignard
2018-11-14 9:00 ` [PATCH v4 4/4] ARM: dts: stm32: enable hwspinlock on stm32mp157c-ed1 Benjamin Gaignard
2018-11-30 14:45 ` [PATCH v4 0/4] Add support of STM32 hwspinlock Benjamin Gaignard
2018-12-04 20:47 ` Rob Herring
2018-12-06 1:10 ` Bjorn Andersson [this message]
2018-12-06 9:10 ` Benjamin Gaignard
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=20181206011045.GA23336@builder \
--to=bjorn.andersson@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=ohad@wizery.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;
as well as URLs for NNTP newsgroup(s).