From: Markus Elfring <Markus.Elfring@web.de>
To: Kuro Chung <kuro.chung@ite.corp-partner.google.com>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Allen Chen <allen.chen@ite.com.tw>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Kenneth Haung <kenneth.hung@ite.com.tw>,
Kuro Chung <kuro.chung@ite.com.tw>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Pin-yen Lin <treapking@chromium.org>,
Robert Foss <rfoss@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v8] drm/bridge: it6505: fix hibernate to resume no display issue
Date: Wed, 15 May 2024 11:50:17 +0200 [thread overview]
Message-ID: <b0c57221-25d1-418e-85ce-d5a8d31a674f@web.de> (raw)
In-Reply-To: <20240515072328.1010920-2-kuro.chung@ite.com.tw>
I suggest to reconsider the distribution of email addresses over recipient lists
once more.
…
> But the input FIFO reset will also trigger error interrupts of output module rising.
> Thus, it6505 have to wait a period can clear those expected error interrupts
> caused by manual hardware reset in one interrupt handler calling to avoid interrupt looping.
* Please reconsider also the usage of word wrapping in such text lines.
* Will another imperative wording be desirable for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n94
* Would you like to add the tag “Fixes”?
Regards,
Markus
parent reply other threads:[~2024-05-15 9:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240515072328.1010920-2-kuro.chung@ite.com.tw>]
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=b0c57221-25d1-418e-85ce-d5a8d31a674f@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=allen.chen@ite.com.tw \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kenneth.hung@ite.com.tw \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuro.chung@ite.com.tw \
--cc=kuro.chung@ite.corp-partner.google.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=treapking@chromium.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).