From: Linus Walleij <linus.walleij@linaro.org>
To: Cong Yang <yangcong5@huaqin.corp-partner.google.com>
Cc: sam@ravnborg.org, neil.armstrong@linaro.org, daniel@ffwll.ch,
dianders@google.com, hsinyi@google.com, swboyd@chromium.org,
airlied@gmail.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v1 0/2] Break out as separate driver from boe-tv101wum-nl6 panel driver
Date: Sun, 8 Oct 2023 21:33:29 +0200 [thread overview]
Message-ID: <CACRpkdbek0-Vhk4_34qY+0=EGrQxJS_CfLuF_5fRozMMyc+=Kw@mail.gmail.com> (raw)
In-Reply-To: <20231007060639.725350-1-yangcong5@huaqin.corp-partner.google.com>
On Sat, Oct 7, 2023 at 8:06 AM Cong Yang
<yangcong5@huaqin.corp-partner.google.com> wrote:
> Linus series proposed to break out ili9882t as separate driver,
> but he didn't have time for that extensive rework of the driver.
> As discussed by Linus and Doug [1], keep macro using the "struct panel_init_cmd"
> until we get some resolution about the binary size issue.
OK works for me:
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Dough, if it looks OK to you too, can you apply the patches?
Yours,
Linus Walleij
next parent reply other threads:[~2023-10-08 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231007060639.725350-1-yangcong5@huaqin.corp-partner.google.com>
2023-10-08 19:33 ` Linus Walleij [this message]
2023-10-09 20:53 ` [v1 0/2] Break out as separate driver from boe-tv101wum-nl6 panel driver Doug Anderson
2023-10-09 21:02 ` Linus Walleij
2023-10-09 21:12 ` Doug Anderson
[not found] ` <20231007060639.725350-2-yangcong5@huaqin.corp-partner.google.com>
2023-10-09 20:44 ` [v1 1/2] drm/panel: ili9882t: Break out as separate driver Doug Anderson
2023-10-10 11:21 ` cong yang
[not found] ` <20231007060639.725350-3-yangcong5@huaqin.corp-partner.google.com>
2023-10-09 20:44 ` [v1 2/2] drm/panel: ili9882t: Avoid blurred screen from fast sleep Doug Anderson
2023-10-10 11:36 ` cong yang
2023-10-10 19:11 ` Doug Anderson
2023-10-11 5:47 ` cong yang
2023-10-12 12:09 ` cong yang
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='CACRpkdbek0-Vhk4_34qY+0=EGrQxJS_CfLuF_5fRozMMyc+=Kw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=sam@ravnborg.org \
--cc=swboyd@chromium.org \
--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).