From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Amelie Delaunay <amelie.delaunay@st.com>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Applied "spi: Document the STM32 SPI bindings" to the spi tree
Date: Tue, 27 Jun 2017 02:10:01 +0100 [thread overview]
Message-ID: <20170627011001.hnj7nbr6h7fqkxdn@sirena.org.uk> (raw)
In-Reply-To: <20170626182240.vcv4wwu7cavgu4na@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
On Mon, Jun 26, 2017 at 01:22:40PM -0500, Rob Herring wrote:
> A bit quick on the applying as there are several comments...
Really trivial things which can easily be fixed incrementally without
having to repeatedly review the entire driver.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-06-27 1:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 14:32 [PATCH 0/2] Add support for STM32 SPI Amelie Delaunay
2017-06-21 14:32 ` [PATCH 1/2] dt-bindings: spi: Document the STM32 SPI bindings Amelie Delaunay
2017-06-21 15:16 ` Applied "spi: Document the STM32 SPI bindings" to the spi tree Mark Brown
2017-06-26 18:22 ` Rob Herring
2017-06-27 1:10 ` Mark Brown [this message]
2017-06-21 15:20 ` [PATCH 1/2] dt-bindings: spi: Document the STM32 SPI bindings Neil Armstrong
2017-06-22 11:51 ` Amelie DELAUNAY
2017-06-26 18:21 ` Rob Herring
2017-06-27 7:38 ` Amelie DELAUNAY
2017-06-21 14:32 ` [PATCH 2/2] spi: add driver for STM32 SPI controller Amelie Delaunay
2017-06-21 15:13 ` Mark Brown
2017-06-22 11:51 ` Amelie DELAUNAY
2017-06-21 15:16 ` Applied "spi: add driver for STM32 SPI controller" to the spi tree Mark Brown
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=20170627011001.hnj7nbr6h7fqkxdn@sirena.org.uk \
--to=broonie@kernel.org \
--cc=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-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@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).