All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Watts <contact@jookia.org>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Priit Laes <plaes@plaes.org>,
	Jessica Zhang <quic_jesszhan@quicinc.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>,
	Ryan Walklin <ryan@testtoast.com>,
	Christophe Branchereau <cbranchereau@gmail.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panel: nv3052c: Reduce duplication of init sequences
Date: Thu, 23 Oct 2025 17:11:18 +1100	[thread overview]
Message-ID: <aPnHBpyhYhMFumPO@titan> (raw)
In-Reply-To: <a6d1e281-2ba4-4b47-86b6-5bf57fa0b71a@linaro.org>

On Mon, Jun 30, 2025 at 05:32:04PM +0200, Neil Armstrong wrote:
> Hi,
> 
> On 19/06/2025 15:22, Priit Laes wrote:
> > Although there are various small changes between the init
> > sequences, the second half is common for all 3 currently
> > supported displays.
> > 
> > Note that this is only compile-tested.
> > 
> > Signed-off-by: Priit Laes <plaes@plaes.org>
> 
> If you can find someone to test this patchset, I'll apply it because it looks good!
> 
> Thanks,
> Neil

Hi there,

Sorry for the very long wait.
I finally got around to reviewing and testing this on the FS035VG158 panel.
The code looks good and works on the panel. I don't see why it won't work on other panels.

Tested-by: John Watts <contact@jookia.org>
Reviewed-by: John Watts <contact@jookia.org>

John.

  reply	other threads:[~2025-10-23  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 13:22 [PATCH] drm/panel: nv3052c: Reduce duplication of init sequences Priit Laes
2025-06-30 15:32 ` Neil Armstrong
2025-10-23  6:11   ` John Watts [this message]
2025-10-29 21:05 ` Neil Armstrong

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=aPnHBpyhYhMFumPO@titan \
    --to=contact@jookia.org \
    --cc=airlied@gmail.com \
    --cc=cbranchereau@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=plaes@plaes.org \
    --cc=quic_jesszhan@quicinc.com \
    --cc=ryan@testtoast.com \
    --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.