From: Imre Deak <imre.deak@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 4/5] drm/i915/dp_tunnel: Sanitize documentation of intel_dp_tunnel_detect()
Date: Mon, 23 Feb 2026 18:45:25 +0200 [thread overview]
Message-ID: <aZyEJdyNxEgazSSF@ideak-desk.lan> (raw)
In-Reply-To: <IA0PR11MB7307ED11D322F4B53B76988FBA77A@IA0PR11MB7307.namprd11.prod.outlook.com>
On Mon, Feb 23, 2026 at 06:12:23PM +0200, Murthy, Arun R wrote:
>
> > -----Original Message-----
> > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Imre
> > Deak
> > Sent: Thursday, February 19, 2026 11:58 PM
> > To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
> > Subject: [PATCH 4/5] drm/i915/dp_tunnel: Sanitize documentation of
> > intel_dp_tunnel_detect()
> >
> > Clarify the documentation of detect_new_tunnel() return values, including the
> > failure case.
> >
>
> Can this change be merged with the previous patch as the previous
> patch makes this change.
There is no functional change. This patch merely clarifies the
formatting of the return value documentation and documents the failure
case, which was already possible before this patchset. Therefore, I
think this is a separate change that should be submitted as a separate
patch.
> Thanks and Regards,
> Arun R Murthy
> -------------------
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_dp_tunnel.c | 9 ++++++---
> > 1 file changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > index 5840b92dace19..1c552a7091897 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_tunnel.c
> > @@ -241,9 +241,12 @@ static int detect_new_tunnel(struct intel_dp
> > *intel_dp, struct drm_modeset_acqui
> > * tunnel. If the tunnel's state change requires this - for instance the
> > * tunnel's group ID has changed - the tunnel will be dropped and recreated.
> > *
> > - * Return 0 in case of success - after any tunnel detected and added to
> > - * @intel_dp - 1 in case the BW on an already existing tunnel has changed in a
> > - * way that requires notifying user space.
> > + * Returns:
> > + * - 0 in case of success - after any tunnel detected and added to
> > + @intel_dp
> > + * - 1 in case the link BW via the new or an already existing tunnel has
> > changed
> > + * in a way that requires notifying user space
> > + * - Negative error code, if creating a new tunnel or updating the tunnel
> > + * state failed
> > */
> > int intel_dp_tunnel_detect(struct intel_dp *intel_dp, struct
> > drm_modeset_acquire_ctx *ctx) {
> > --
> > 2.49.1
>
next prev parent reply other threads:[~2026-02-23 16:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 18:28 [PATCH 0/5] drm/i915/dp_tunnel: Preparation for UHBR DP tunnels Imre Deak
2026-02-19 18:28 ` [PATCH 1/5] drm/i915/dp_tunnel: Don't update tunnel state during system resume Imre Deak
2026-02-23 15:54 ` Murthy, Arun R
2026-02-23 16:30 ` Imre Deak
2026-02-24 2:33 ` Murthy, Arun R
2026-02-24 7:49 ` Imre Deak
2026-02-24 12:55 ` Murthy, Arun R
2026-02-19 18:28 ` [PATCH 2/5] drm/i915/dp_tunnel: Simplify detection of link BW change Imre Deak
2026-02-23 16:02 ` Murthy, Arun R
2026-02-23 16:35 ` Imre Deak
2026-02-24 12:56 ` Murthy, Arun R
2026-02-19 18:28 ` [PATCH 3/5] drm/i915/dp_tunnel: Split update_tunnel_state() Imre Deak
2026-02-24 12:57 ` Murthy, Arun R
2026-02-19 18:28 ` [PATCH 4/5] drm/i915/dp_tunnel: Sanitize documentation of intel_dp_tunnel_detect() Imre Deak
2026-02-23 16:12 ` Murthy, Arun R
2026-02-23 16:45 ` Imre Deak [this message]
2026-02-24 2:36 ` Murthy, Arun R
2026-02-24 7:55 ` Imre Deak
2026-02-24 12:55 ` Murthy, Arun R
2026-02-19 18:28 ` [PATCH 5/5] drm/i915/dp_tunnel: Send BW change notification after tunnel creation Imre Deak
2026-02-24 12:58 ` Murthy, Arun R
2026-02-19 19:28 ` ✓ CI.KUnit: success for drm/i915/dp_tunnel: Preparation for UHBR DP tunnels Patchwork
2026-02-20 8:42 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-20 13:42 ` ✗ Xe.CI.FULL: failure " Patchwork
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=aZyEJdyNxEgazSSF@ideak-desk.lan \
--to=imre.deak@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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