From: Mario Limonciello <superm1@kernel.org>
To: "Eren Özen" <erenozen@protonmail.com>
Cc: Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Richard Hughes <richard@hughsie.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Wayne Lin <Wayne.Lin@amd.com>,
simonit.orig@gmail.com
Subject: Re: [PATCH v4] drm/amd/display: Route connector DDC over AUX for native DP sinks
Date: Thu, 19 Nov 2026 05:23:17 -0600 [thread overview]
Message-ID: <53b5fa1b-9c26-4493-a5fc-7d0393b53abd@kernel.org> (raw)
In-Reply-To: <oUnLboT5nQrS84FGA16aamWt5D9VXEosZZdV3BIUQ1cu4drCXXKDR3kPP0vGvglmf0jXGMvoaYLI1jYamvaz4Zdd2D-6BJ-7I9bv3eZylm4=@protonmail.com>
On 11/19/26 02:36, Eren Özen wrote:
> Hi Mario,
>
> Thanks for folding it in and for the credit. My part was written with
> help from an AI assistant, so per Documentation/process/coding-assistants.rst
> as far as I understand, the commit should also carry:
>
> Assisted-by: Claude:claude-opus-5-5
>
> Could you add it when this gets applied?
>
> Thanks,
> Eren
Actually the kernel dropped the policy for documenting this requirement.
So no need to add it.
I still do have feedback from Sashiko about the swapping to a passive
DP++ dongle. But I'd like to know from Simon if this even conceptually
works.
So Simon please test this patch against the original issue.
If you need some help building the kernel, I suggest working with an LLM
on your specific distro, they're pretty good at helping with this kind
of thing.
prev parent reply other threads:[~2026-11-19 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 5:17 [PATCH v4] drm/amd/display: Route connector DDC over AUX for native DP sinks Mario Limonciello
2026-11-19 5:35 ` sashiko-bot
2026-11-19 8:36 ` Eren Özen
2026-11-19 11:23 ` Mario Limonciello [this message]
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=53b5fa1b-9c26-4493-a5fc-7d0393b53abd@kernel.org \
--to=superm1@kernel.org \
--cc=Wayne.Lin@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=erenozen@protonmail.com \
--cc=harry.wentland@amd.com \
--cc=richard@hughsie.com \
--cc=simonit.orig@gmail.com \
--cc=sunpeng.li@amd.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.