From: Archit More <architmore303@gmail.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Douglas Anderson <dianders@chromium.org>
Cc: Akash Sukhavasi <akash.sukhavasi@gmail.com>,
Chris Morgan <macromorgan@hotmail.com>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Archit More <architmore303@gmail.com>
Subject: [PATCH 0/3] drm/panel: Use lowercase hex literals in three panel drivers
Date: Thu, 19 Nov 2026 21:53:50 +0530 [thread overview]
Message-ID: <20261119162353.12962-1-architmore303@gmail.com> (raw)
Convert hexadecimal literals in the initialization sequences of
newvision-nv3051d, kingdisplay-kd097d04, and leadtek-ltk500hd1829 to
lowercase, as suggested by Douglas Anderson.
Archit More (3):
drm/panel: newvision-nv3051d: Use lowercase hex literals
drm/panel: kingdisplay-kd097d04: Use lowercase hex literals
drm/panel: leadtek-ltk500hd1829: Use lowercase hex literals
.../drm/panel/panel-kingdisplay-kd097d04.c | 242 +++++-----
.../drm/panel/panel-leadtek-ltk500hd1829.c | 426 +++++++++---------
.../gpu/drm/panel/panel-newvision-nv3051d.c | 286 ++++++------
3 files changed, 477 insertions(+), 477 deletions(-)
--
2.34.1
next reply other threads:[~2026-11-19 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 16:23 Archit More [this message]
2026-11-19 16:23 ` [PATCH 1/3] drm/panel: newvision-nv3051d: Use lowercase hex literals Archit More
2026-11-19 16:23 ` [PATCH 2/3] drm/panel: kingdisplay-kd097d04: " Archit More
2026-11-19 16:23 ` [PATCH 3/3] drm/panel: leadtek-ltk500hd1829: " Archit More
2026-11-19 22:00 ` [PATCH 0/3] drm/panel: Use lowercase hex literals in three panel drivers Doug Anderson
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=20261119162353.12962-1-architmore303@gmail.com \
--to=architmore303@gmail.com \
--cc=airlied@gmail.com \
--cc=akash.sukhavasi@gmail.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.