From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/panel: Rename Sony ACX424 to Novatek NT35560
Date: Sat, 19 Feb 2022 10:13:52 +0100 [thread overview]
Message-ID: <YhC00FbY/W1r9m6T@ravnborg.org> (raw)
In-Reply-To: <CACRpkdZ2tUKuGP4SZdar=9tMVO__xn0fUV+DQGU5PRwcPo9ERA@mail.gmail.com>
Hi Linus,
On Sat, Feb 19, 2022 at 02:40:33AM +0100, Linus Walleij wrote:
> On Sat, Jan 29, 2022 at 2:26 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > On Mon, Jan 3, 2022 at 12:40 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > > A code drop from Sony Mobile reveals that the ACX424 panels are
> > > built around the Novatek NT35560 panel controllers so just bite
> > > the bullet and rename the driver and all basic symbols so that
> > > we can modify this driver to cover any other panels also using
> > > the Novatek NT35560 display controller.
> > >
> > > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > Could someone take mercy in reviewing this patch set?
> >
> > I can offer some patch review back!
>
> I can also offer coffee in person in Sweden,
I will take you up on this on day - I hope :-)
Greetings from Denmark.
Sam
next prev parent reply other threads:[~2022-02-19 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 11:38 [PATCH 1/3] drm/panel: Rename Sony ACX424 to Novatek NT35560 Linus Walleij
2022-01-03 11:38 ` [PATCH 2/3] drm/panel: nt35560: Support more panel IDs Linus Walleij
2022-02-19 9:17 ` Sam Ravnborg
2022-01-03 11:38 ` [PATCH 3/3] drm/panel: nt35560: Support also ACX424AKM Linus Walleij
2022-02-19 9:20 ` Sam Ravnborg
2022-01-29 1:26 ` [PATCH 1/3] drm/panel: Rename Sony ACX424 to Novatek NT35560 Linus Walleij
2022-02-19 1:40 ` Linus Walleij
2022-02-19 9:13 ` Sam Ravnborg [this message]
2022-02-19 9:15 ` Sam Ravnborg
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=YhC00FbY/W1r9m6T@ravnborg.org \
--to=sam@ravnborg.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linus.walleij@linaro.org \
--cc=thierry.reding@gmail.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