All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Jani Nikula" <jani.nikula@intel.com>
Subject: Re: [PATCH v3 0/2] Improve type-safety on POWER_DOMAIN_*() macros
Date: Thu, 27 Feb 2025 18:12:41 -0300	[thread overview]
Message-ID: <174069076162.19033.18196476050088822843@intel.com> (raw)
In-Reply-To: <20250227-improve-type-safey-power-domain-macros-v3-0-b6eaa00f9c33@intel.com>

Whoops... This should've been v4. Let's see how Patchwork and CI will
react.

--
Gustavo Sousa

Quoting Gustavo Sousa (2025-02-27 18:09:11-03:00)
>Fix one issue[1] reported by the kernel test robot and also take this
>opportunity to improve POWER_DOMAIN_*() macros by making them explicitly
>return the expected enum type with patch #2.
>
>I decided to send this new version with patch #3 dropped in order to get
>CI results and merge the already reviewed patches #1 and #2. Patch #3
>from the previous version is still under discussion and will probably be
>respinned as a standalone patch.
>
>[1] https://lore.kernel.org/oe-kbuild-all/202502120809.XfmcqkBD-lkp@intel.com/
>
>---
>Gustavo Sousa (2):
>      drm/i915/display: Use explicit base values in POWER_DOMAIN_*() macros
>      drm/i915/display: Make POWER_DOMAIN_*() always result in enum intel_display_power_domain
>
> drivers/gpu/drm/i915/display/intel_display_power.h | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>---
>base-commit: 6badede10d92c242241bd7bf59a5488b5eba5aa7
>change-id: 20250227-improve-type-safey-power-domain-macros-8bf2a14f43f9
>
>Best regards,
>-- 
>Gustavo Sousa <gustavo.sousa@intel.com>
>

  parent reply	other threads:[~2025-02-27 21:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 21:09 [PATCH v3 0/2] Improve type-safety on POWER_DOMAIN_*() macros Gustavo Sousa
2025-02-27 21:09 ` [PATCH v3 1/2] drm/i915/display: Use explicit base values in " Gustavo Sousa
2025-02-27 21:09 ` [PATCH v3 2/2] drm/i915/display: Make POWER_DOMAIN_*() always result in enum intel_display_power_domain Gustavo Sousa
2025-02-27 21:12 ` Gustavo Sousa [this message]
2025-02-27 23:23 ` ✓ CI.Patch_applied: success for Improve type-safety on POWER_DOMAIN_*() macros (rev4) Patchwork
2025-02-27 23:23 ` ✓ CI.checkpatch: " Patchwork
2025-02-27 23:25 ` ✓ CI.KUnit: " Patchwork
2025-02-27 23:41 ` ✓ CI.Build: " Patchwork
2025-02-27 23:44 ` ✓ CI.Hooks: " Patchwork
2025-02-27 23:45 ` ✓ CI.checksparse: " Patchwork
2025-02-28  0:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-28  0:12 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2025-02-28  0:32 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-28  4:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-28 16:02   ` Gustavo Sousa
2025-02-28 10:09 ` ✗ i915.CI.Full: " Patchwork
2025-02-28 16:27   ` Gustavo Sousa
2025-02-28 16:48 ` [PATCH v3 0/2] Improve type-safety on POWER_DOMAIN_*() macros Gustavo Sousa

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=174069076162.19033.18196476050088822843@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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 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.