From: Mark Brown <broonie@kernel.org>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
James Hartley <James.Hartley@imgtec.com>,
Ezequiel Garcia <Ezequiel.Garcia@imgtec.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: [PATCH 1/2] of: Add binding document for IMG SPFI controller
Date: Wed, 12 Nov 2014 22:09:35 +0000 [thread overview]
Message-ID: <20141112220935.GS3815@sirena.org.uk> (raw)
In-Reply-To: <1415828274-24727-2-git-send-email-abrestic@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Wed, Nov 12, 2014 at 01:37:53PM -0800, Andrew Bresticker wrote:
> The Synchronous Peripheral Flash Interface (SPFI) controller found
> on IMG SoCs supports single, dual, and (optionally) quad mode SPI
> transfers.
This is OK but please use subject lines matching the style for the
subsystem; people often filter on subject line when describing what to
read. I do note that the binding lists the DMA as mandatory but the
implementation tolerates it being missing, this is fine since the code
is more liberal.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-12 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 21:37 [PATCH 0/2] IMG SPFI driver Andrew Bresticker
2014-11-12 21:37 ` [PATCH 1/2] of: Add binding document for IMG SPFI controller Andrew Bresticker
2014-11-12 22:09 ` Mark Brown [this message]
2014-11-12 21:37 ` [PATCH 2/2] spi: Add driver " Andrew Bresticker
2014-11-12 22:07 ` Mark Brown
2014-11-12 22:54 ` Andrew Bresticker
2014-11-12 23:06 ` Mark Brown
2014-11-13 15:07 ` James Hartley
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=20141112220935.GS3815@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Ezequiel.Garcia@imgtec.com \
--cc=James.Hartley@imgtec.com \
--cc=abrestic@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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®