From: Doug Anderson <dianders@google.com>
To: yangcong <yangcong5@huaqin.corp-partner.google.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v4 4/4] dt-bindngs: display: panel: Add BOE and INX panel bindings
Date: Wed, 8 Sep 2021 07:45:29 -0700 [thread overview]
Message-ID: <CAD=FV=XzUUdh-hTTg_Pv1P8WHwTTXa7F5m6q1xq=XVdPxyDDpw@mail.gmail.com> (raw)
In-Reply-To: <20210830023849.258839-5-yangcong5@huaqin.corp-partner.google.com>
Hi,
On Sun, Aug 29, 2021 at 7:39 PM yangcong
<yangcong5@huaqin.corp-partner.google.com> wrote:
>
> Add documentation for boe tv110c9m-ll3, inx hj110iz-01a panel.
>
> Signed-off-by: yangcong <yangcong5@huaqin.corp-partner.google.com>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
> ---
> .../devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
Not worth re-posting just for this, but when applying we should fix
s/bindngs/bindings/ in ${SUBJECT}. If you end up posting a v5 for some
other reason then you should fix it, of course.
-Doug
prev parent reply other threads:[~2021-09-08 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 2:38 [v4 0/4] drm/panel: boe-tv101wum-nl6: Support enabling a 3.3V rail yangcong
2021-08-30 2:38 ` [v4 1/4] " yangcong
2021-08-30 2:38 ` [v4 2/4] dt-bindings: " yangcong
2021-08-30 2:38 ` [v4 3/4] drm/panel: support for BOE and INX video mode panel yangcong
2021-08-30 16:17 ` Doug Anderson
2021-08-30 2:38 ` [v4 4/4] dt-bindngs: display: panel: Add BOE and INX panel bindings yangcong
2021-08-31 22:32 ` Rob Herring
2021-09-08 14:45 ` Doug Anderson [this message]
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='CAD=FV=XzUUdh-hTTg_Pv1P8WHwTTXa7F5m6q1xq=XVdPxyDDpw@mail.gmail.com' \
--to=dianders@google.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=yangcong5@huaqin.corp-partner.google.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).