From: Jani Nikula <jani.nikula@intel.com>
To: Wayne Lin <Wayne.Lin@amd.com>, dri-devel@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, mario.limonciello@amd.com,
harry.wentland@amd.com, Wayne Lin <Wayne.Lin@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/dp: Fix Write_Status_Update_Request AUX request format
Date: Thu, 08 May 2025 11:19:08 +0300 [thread overview]
Message-ID: <877c2rv7k3.fsf@intel.com> (raw)
In-Reply-To: <20250427095053.875064-1-Wayne.Lin@amd.com>
On Sun, 27 Apr 2025, Wayne Lin <Wayne.Lin@amd.com> wrote:
> + /*
> + * When I2C write firstly get defer and get ack after
> + * retries by wirte_status_update, we have to return
> + * all data bytes get transferred instead of 0.
> + */
My brain gives me syntax and parse error here. ;)
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-08 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 9:50 [PATCH] drm/dp: Fix Write_Status_Update_Request AUX request format Wayne Lin
2025-05-05 20:22 ` Mario Limonciello
2025-05-08 1:48 ` Lin, Wayne
2025-05-08 8:19 ` Jani Nikula [this message]
2025-05-08 12:02 ` Lin, Wayne
2025-05-08 12:16 ` Jani Nikula
2025-05-08 12:54 ` Lin, Wayne
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=877c2rv7k3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Wayne.Lin@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=mario.limonciello@amd.com \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.intel.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).