From: Rob Herring <robh@kernel.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Russell King <linux@armlinux.org.uk>,
Mark Rutland <mark.rutland@arm.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] dt-bindings: display: armada: Improve the LCDC documentation
Date: Mon, 25 Mar 2019 14:15:48 -0500 [thread overview]
Message-ID: <20190325191548.GA1323@bogus> (raw)
In-Reply-To: <20190320082057.856943-4-lkundrak@v3.sk>
On Wed, Mar 20, 2019 at 09:20:55AM +0100, Lubomir Rintel wrote:
> The port is a child, not a property. And should be accompanied by an
> example. Plus a pair of cosmetic changes that don't seem to deserve a
> separate commit.
>
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
>
> ---
> Changes since v2:
> - Collected the Reviewed-by tag
Really, where?
> Changes since v1:
> - Minor adjustments to the commit message wording.
>
> .../bindings/display/marvell,armada-lcdc.txt | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2019-03-25 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 8:20 [PATCH v3 0/5] dt-bindings: improve the Armada DRM bindings Lubomir Rintel
2019-03-20 8:20 ` [PATCH v3 1/5] dt-bindings: reserved-memory: Add binding for Armada framebuffer Lubomir Rintel
2019-03-20 8:20 ` [PATCH v3 2/5] dt-bindings: display: armada: Rename the binding doc file Lubomir Rintel
2019-03-20 8:20 ` [PATCH v3 3/5] dt-bindings: display: armada: Improve the LCDC documentation Lubomir Rintel
2019-03-25 19:15 ` Rob Herring [this message]
2019-03-20 8:20 ` [PATCH v3 4/5] dt-bindings: display: armada: Add more compatible strings Lubomir Rintel
2019-03-28 17:52 ` Rob Herring
2019-03-20 8:20 ` [PATCH v3 5/5] dt-bindings: display: armada: Document bus-width property Lubomir Rintel
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=20190325191548.GA1323@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
/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).