From: Gareth Williams <gareth.williams.jx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Phil Edworthy <phil.edworthy@renesas.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/2] dt: snps,dw-apb-ssi: Add clock bindings documentation
Date: Mon, 11 Mar 2019 11:50:55 +0000 [thread overview]
Message-ID: <TYAPR01MB401574D8B0996378DCD5DC97DF480@TYAPR01MB4015.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190303233145.GN23441@sirena.org.uk>
> On Sat, Mar 03, 2019 at 23:32 +0100, Mark Brown wrote:
> > On Thu, Feb 28, 2019 at 01:25:41PM +0000, Gareth Williams wrote:
> > From: Phil Edworthy <phil.edworthy@renesas.com>
> >
> > The driver requires a clock property, so detail it in the docs.
> > Fix a typo, 'pis' to 'pins'.
> > Add documentation for a separate, optional, interface clock.
>
> Please use subject lines matching the style for the subsystem. This makes it
> easier for people to identify relevant patches.
Thanks for the feedback Mark.
I will wait another week to see if there is any other feedback before sending an updated version of this patch series.
next prev parent reply other threads:[~2019-03-11 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 13:25 [PATCH 0/2] spi: dw: Add support for an optional interface clock Gareth Williams
2019-02-28 13:25 ` [PATCH 1/2] dt: snps,dw-apb-ssi: Add clock bindings documentation Gareth Williams
2019-03-03 23:31 ` Mark Brown
2019-03-11 11:50 ` Gareth Williams [this message]
2019-02-28 13:25 ` [PATCH 2/2] spi: dw: Add support for an optional interface clock Gareth Williams
2019-03-04 0:04 ` Mark Brown
2019-03-04 14:46 ` Gareth Williams
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=TYAPR01MB401574D8B0996378DCD5DC97DF480@TYAPR01MB4015.jpnprd01.prod.outlook.com \
--to=gareth.williams.jx@renesas.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=phil.edworthy@renesas.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®