From: Brian Dodge <bdodge09@gmail.com>
To: pavel@ucw.cz
Cc: devicetree@vger.kernel.org, daniel.thompson@linaro.org,
jingoohan1@gmail.com, dri-devel@lists.freedesktop.org,
robh+dt@kernel.org, jacek.anaszewski@gmail.com, pbacon@psemi.com,
lee.jones@linaro.org, linux-leds@vger.kernel.org
Subject: [PATCH 0/2] fix vendor prefix for arcxcnn driver and bindings
Date: Tue, 25 Jun 2019 00:05:27 -0400 [thread overview]
Message-ID: <1561435529-7835-1-git-send-email-bdodge09@gmail.com> (raw)
These two patches supercede the prior similar three-patch set
submitted on 6 Mov 2018. Apologies for the confusion.
This patch is to update the arcxcnn backlight driver to use the
proper "arctic" vendor-prefix and document that in the device-
tree bindings.
There is at least one existing device using the old "arc"
vendor-prefix (Samsung Chromebook Plus), so support for that
remains in the driver source.
Unlike the previous patch set which hasn't been applied, there
there is no actual functionality change here.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-06-25 4:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 4:05 Brian Dodge [this message]
2019-06-25 4:05 ` [PATCH 1/2] dt-bindings: backlight: fix vendor prefix for ArcticSand arcxcnn driver bindings Brian Dodge
2019-06-25 8:55 ` Daniel Thompson
2019-06-25 11:44 ` Brian Dodge
2019-06-26 10:56 ` Daniel Thompson
2019-06-26 13:22 ` Lee Jones
2019-06-26 14:43 ` Rob Herring
2019-06-26 14:56 ` Pavel Machek
2019-06-26 14:59 ` Brian Dodge
2019-06-26 15:09 ` Dan Murphy
2019-06-26 11:44 ` Dan Murphy
2019-06-25 4:05 ` [PATCH 2/2] backlight: arcxcnn: add "arctic" vendor prefix Brian Dodge
2019-06-26 10:53 ` Daniel Thompson
2019-06-26 11:42 ` Dan Murphy
2019-06-26 11:45 ` Dan Murphy
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=1561435529-7835-1-git-send-email-bdodge09@gmail.com \
--to=bdodge09@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=pbacon@psemi.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;
as well as URLs for NNTP newsgroup(s).