From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: drop intel_dpio_phy.h include from VLV IOSF SB
Date: Tue, 27 May 2025 15:10:37 -0400 [thread overview]
Message-ID: <aDYOLVN-HHuVGvpT@intel.com> (raw)
In-Reply-To: <20250527114854.3687469-1-jani.nikula@intel.com>
On Tue, May 27, 2025 at 02:48:54PM +0300, Jani Nikula wrote:
> vlv_iosf_sb.c no longer depends on enum dpio_phy from
> intel_dpio_phy.h. Drop the include.
Trusting more your compiler then my eyes:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/vlv_iosf_sb.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/vlv_iosf_sb.c b/drivers/gpu/drm/i915/vlv_iosf_sb.c
> index f4b435555f3b..f4b386933141 100644
> --- a/drivers/gpu/drm/i915/vlv_iosf_sb.c
> +++ b/drivers/gpu/drm/i915/vlv_iosf_sb.c
> @@ -8,8 +8,6 @@
> #include "i915_reg.h"
> #include "vlv_iosf_sb.h"
>
> -#include "display/intel_dpio_phy.h"
> -
> /*
> * IOSF sideband, see VLV2_SidebandMsg_HAS.docx and
> * VLV_VLV2_PUNIT_HAS_0.8.docx
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-05-27 19:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 11:48 [PATCH] drm/i915: drop intel_dpio_phy.h include from VLV IOSF SB Jani Nikula
2025-05-27 16:48 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-05-27 19:10 ` Rodrigo Vivi [this message]
2025-05-27 21:02 ` ✓ i915.CI.BAT: success for drm/i915: drop intel_dpio_phy.h include from VLV IOSF SB (rev2) Patchwork
2025-05-27 21:04 ` ✓ CI.Patch_applied: success for drm/i915: drop intel_dpio_phy.h include from VLV IOSF SB Patchwork
2025-05-27 21:05 ` ✓ CI.checkpatch: " Patchwork
2025-05-27 21:07 ` ✓ CI.KUnit: " Patchwork
2025-05-27 21:11 ` ✗ CI.Build: failure " Patchwork
2025-05-28 0:08 ` ✗ i915.CI.Full: failure for drm/i915: drop intel_dpio_phy.h include from VLV IOSF SB (rev2) Patchwork
2025-05-28 6:07 ` ✓ CI.Patch_applied: success for drm/i915: drop intel_dpio_phy.h include from VLV IOSF SB Patchwork
2025-05-28 6:07 ` ✓ CI.checkpatch: " Patchwork
2025-05-28 6:08 ` ✓ CI.KUnit: " Patchwork
2025-05-28 6:12 ` ✗ CI.Build: failure " Patchwork
2025-05-28 6:15 ` ✗ CI.Patch_applied: " Patchwork
2025-05-28 6:20 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-28 6:21 ` ✓ CI.checkpatch: " Patchwork
2025-05-28 6:22 ` ✓ CI.KUnit: " Patchwork
2025-05-28 6:25 ` ✗ CI.Build: failure " Patchwork
2025-05-28 6:27 ` ✗ CI.Patch_applied: " Patchwork
2025-05-28 6:32 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-28 6:32 ` ✓ CI.checkpatch: " Patchwork
2025-05-28 6:33 ` ✓ CI.KUnit: " Patchwork
2025-05-28 6:37 ` ✗ CI.Build: 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=aDYOLVN-HHuVGvpT@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 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.