From: Jani Nikula <jani.nikula@linux.intel.com>
To: "xinlei.lee" <xinlei.lee@mediatek.com>,
chunkuang.hu@kernel.org, p.zabel@pengutronix.de,
airlied@linux.ie, daniel@ffwll.ch, matthias.bgg@gmail.com
Cc: jitao.shi@mediatek.com, allen-kh.cheng@mediatek.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-mediatek@lists.infradead.org, rex-bc.chen@mediatek.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2, 0/4] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence
Date: Tue, 08 Mar 2022 12:21:42 +0200 [thread overview]
Message-ID: <87tuc8218p.fsf@intel.com> (raw)
In-Reply-To: <9e3cd215a2f771236855bdb2f5faa172dcbd1aec.camel@mediatek.com>
On Tue, 08 Mar 2022, xinlei.lee <xinlei.lee@mediatek.com> wrote:
> On Fri, 2022-03-04 at 13:51 +0200, Jani Nikula wrote:
>> Please also prefix cover letters with drm/mediatek if that's the only
>> place you're touching.
>
> Thanks for your review.
> Is your suggestion for me to put the fix id on the cover ?
Heh, it's not really review, just something to ease me going through the
dri-devel mails in the future.
The cover letter subject is "Cooperate with DSI RX devices to modify dsi
funcs and delay mipi high to cooperate with panel sequence" and I don't
know whether the thread is about drm dsi helpers or some drivers and
what drivers. If the cover letter subject also had the prefix
"drm/mediatek:" like all the patches, I could've just skipped it
altogether.
Just something to consider in the future, no need to do anything here.
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "xinlei.lee" <xinlei.lee@mediatek.com>,
chunkuang.hu@kernel.org, p.zabel@pengutronix.de,
airlied@linux.ie, daniel@ffwll.ch, matthias.bgg@gmail.com
Cc: jitao.shi@mediatek.com, allen-kh.cheng@mediatek.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-mediatek@lists.infradead.org, rex-bc.chen@mediatek.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2, 0/4] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence
Date: Tue, 08 Mar 2022 12:21:42 +0200 [thread overview]
Message-ID: <87tuc8218p.fsf@intel.com> (raw)
In-Reply-To: <9e3cd215a2f771236855bdb2f5faa172dcbd1aec.camel@mediatek.com>
On Tue, 08 Mar 2022, xinlei.lee <xinlei.lee@mediatek.com> wrote:
> On Fri, 2022-03-04 at 13:51 +0200, Jani Nikula wrote:
>> Please also prefix cover letters with drm/mediatek if that's the only
>> place you're touching.
>
> Thanks for your review.
> Is your suggestion for me to put the fix id on the cover ?
Heh, it's not really review, just something to ease me going through the
dri-devel mails in the future.
The cover letter subject is "Cooperate with DSI RX devices to modify dsi
funcs and delay mipi high to cooperate with panel sequence" and I don't
know whether the thread is about drm dsi helpers or some drivers and
what drivers. If the cover letter subject also had the prefix
"drm/mediatek:" like all the patches, I could've just skipped it
altogether.
Just something to consider in the future, no need to do anything here.
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "xinlei.lee" <xinlei.lee@mediatek.com>,
chunkuang.hu@kernel.org, p.zabel@pengutronix.de,
airlied@linux.ie, daniel@ffwll.ch, matthias.bgg@gmail.com
Cc: jitao.shi@mediatek.com, allen-kh.cheng@mediatek.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-mediatek@lists.infradead.org, rex-bc.chen@mediatek.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2, 0/4] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence
Date: Tue, 08 Mar 2022 12:21:42 +0200 [thread overview]
Message-ID: <87tuc8218p.fsf@intel.com> (raw)
In-Reply-To: <9e3cd215a2f771236855bdb2f5faa172dcbd1aec.camel@mediatek.com>
On Tue, 08 Mar 2022, xinlei.lee <xinlei.lee@mediatek.com> wrote:
> On Fri, 2022-03-04 at 13:51 +0200, Jani Nikula wrote:
>> Please also prefix cover letters with drm/mediatek if that's the only
>> place you're touching.
>
> Thanks for your review.
> Is your suggestion for me to put the fix id on the cover ?
Heh, it's not really review, just something to ease me going through the
dri-devel mails in the future.
The cover letter subject is "Cooperate with DSI RX devices to modify dsi
funcs and delay mipi high to cooperate with panel sequence" and I don't
know whether the thread is about drm dsi helpers or some drivers and
what drivers. If the cover letter subject also had the prefix
"drm/mediatek:" like all the patches, I could've just skipped it
altogether.
Just something to consider in the future, no need to do anything here.
Thanks,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-03-08 10:32 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 10:15 [PATCH v2, 0/4] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence xinlei.lee
2022-03-04 10:15 ` [PATCH v2,0/4] " xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 0/4] " xinlei.lee
2022-03-04 10:15 ` xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 1/4] drm/mediatek: Adjust the timing of mipi signal from LP00 to LP11 xinlei.lee
2022-03-04 10:15 ` [PATCH v2,1/4] " xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 1/4] " xinlei.lee
2022-03-04 10:15 ` xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 2/4] drm/mediatek: Separate poweron/poweroff from enable/disable and define new funcs xinlei.lee
2022-03-04 10:15 ` [PATCH v2,2/4] " xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 2/4] " xinlei.lee
2022-03-04 10:15 ` xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 3/4] drm/mediatek: keep dsi as LP00 before dcs cmds transfer xinlei.lee
2022-03-04 10:15 ` [PATCH v2,3/4] " xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 3/4] " xinlei.lee
2022-03-04 10:15 ` xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 4/4] drm/mediatek: Add pull-down MIPI operation in mtk_dsi_poweroff function xinlei.lee
2022-03-04 10:15 ` [PATCH v2,4/4] " xinlei.lee
2022-03-04 10:15 ` [PATCH v2, 4/4] " xinlei.lee
2022-03-04 10:15 ` xinlei.lee
2022-03-04 11:24 ` [PATCH v2, 0/4] Cooperate with DSI RX devices to modify dsi funcs and delay mipi high to cooperate with panel sequence Benjamin Gaignard
2022-03-04 11:24 ` Benjamin Gaignard
2022-03-04 11:24 ` Benjamin Gaignard
2022-03-04 11:24 ` Benjamin Gaignard
2022-03-08 9:12 ` Hsin-Yi Wang
2022-03-08 9:12 ` Hsin-Yi Wang
2022-03-08 9:12 ` Hsin-Yi Wang
2022-03-08 10:00 ` Benjamin Gaignard
2022-03-08 10:00 ` Benjamin Gaignard
2022-03-08 10:00 ` Benjamin Gaignard
2022-03-08 10:00 ` Benjamin Gaignard
2022-03-09 5:55 ` Hsin-Yi Wang
2022-03-09 5:55 ` Hsin-Yi Wang
2022-03-09 5:55 ` Hsin-Yi Wang
2022-03-09 5:55 ` Hsin-Yi Wang
2022-03-10 2:49 ` xinlei.lee
2022-03-10 2:49 ` xinlei.lee
2022-03-10 2:49 ` xinlei.lee
2022-03-10 3:33 ` xinlei.lee
2022-03-10 3:33 ` xinlei.lee
2022-03-10 3:33 ` xinlei.lee
2022-03-10 3:53 ` Hsin-Yi Wang
2022-03-10 3:53 ` Hsin-Yi Wang
2022-03-10 3:53 ` Hsin-Yi Wang
2022-03-10 3:53 ` Hsin-Yi Wang
2022-03-04 11:51 ` Jani Nikula
2022-03-04 11:51 ` Jani Nikula
2022-03-04 11:51 ` Jani Nikula
2022-03-08 10:14 ` xinlei.lee
2022-03-08 10:14 ` xinlei.lee
2022-03-08 10:14 ` xinlei.lee
2022-03-08 10:21 ` Jani Nikula [this message]
2022-03-08 10:21 ` Jani Nikula
2022-03-08 10:21 ` Jani Nikula
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=87tuc8218p.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=allen-kh.cheng@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=rex-bc.chen@mediatek.com \
--cc=xinlei.lee@mediatek.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 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.