All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ville Syrjala" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915/de: Nuke intel_de_{read,write}_notrace()
Date: Wed, 30 Sep 2026 12:01:36 +0000	[thread overview]
Message-ID: <20260930120137.13C581F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930115303.24285-3-ville.syrjala@linux.intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/i915: unused intel_uncore_write_notrace generator leftover
--

commit 63a0967a4211723ada8b8d7082bed7b2f369c08a
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>

drm/i915/de: Nuke intel_de_{read,write}_notrace()

The commit removes the unused intel_de_read_notrace() and 
intel_de_write_notrace() accessors, along with their xe compat wrappers. This 
reduces the number of register access functions to clean up the code between 
i915 and xe.

> diff --git a/drivers/gpu/drm/i915/display/intel_de.h b/drivers/gpu/drm/i915/display/intel_de.h
> index 8144588d3cf77..4ae041a96b31a 100644
> --- a/drivers/gpu/drm/i915/display/intel_de.h
> +++ b/drivers/gpu/drm/i915/display/intel_de.h
> @@ -164,18 +164,6 @@ intel_de_posting_read_fw(struct intel_display *display, intel_reg_t reg)
>  	intel_de_read_fw(display, reg);
>  }
>  
> -static inline u32
> -intel_de_read_notrace(struct intel_display *display, intel_reg_t reg)
> -{
> -	return intel_uncore_read_notrace(__to_uncore(display), reg);
> -}
> -
> -static inline void
> -intel_de_write_notrace(struct intel_display *display, intel_reg_t reg, u32 val)
> -{
> -	intel_uncore_write_notrace(__to_uncore(display), reg, val);
> -}

[Severity: Low]
With the removal of intel_de_write_notrace(), it looks like
intel_uncore_write_notrace() is now unused. Should the macro expansion that
generates it in i915 be removed as well to complete the cleanup?

drivers/gpu/drm/i915/intel_uncore.h:
__uncore_write(write_notrace, 32, l, false)

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260930115303.24285-1-ville.syrjala@linux.intel.com?part=3

  reply	other threads:[~2026-09-30 12:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 11:53 [PATCH 1/3] drm/i915/gmbus: Switch GMBUS fully to _fw() register accesses Ville Syrjala
2026-09-30 11:53 ` [PATCH 2/3] drm/i915/dp: Drop using intel_de_read_notrace() Ville Syrjala
2026-09-30 12:02   ` sashiko-bot
2026-09-30 14:53   ` Jani Nikula
2026-10-01 15:16     ` Jani Nikula
2026-10-02 13:57   ` [PATCH v2 " Ville Syrjala
2026-09-30 11:53 ` [PATCH 3/3] drm/i915/de: Nuke intel_de_{read,write}_notrace() Ville Syrjala
2026-09-30 12:01   ` sashiko-bot [this message]
2026-09-30 14:54   ` Jani Nikula
2026-09-30 12:01 ` ✓ CI.KUnit: success for series starting with [1/3] drm/i915/gmbus: Switch GMBUS fully to _fw() register accesses Patchwork
2026-09-30 12:04 ` [PATCH 1/3] " sashiko-bot
2026-09-30 13:16 ` [PATCH v2 " Ville Syrjala
2026-09-30 14:14   ` Jani Nikula
2026-09-30 13:24 ` ✓ CI.KUnit: success for series starting with [v2,1/3] drm/i915/gmbus: Switch GMBUS fully to _fw() register accesses (rev2) Patchwork
2026-09-30 13:35 ` ✓ Xe.CI.BAT: success for series starting with [1/3] drm/i915/gmbus: Switch GMBUS fully to _fw() register accesses Patchwork
2026-09-30 13:52 ` ✓ i915.CI.BAT: " Patchwork
2026-09-30 15:02 ` ✓ Xe.CI.BAT: success for series starting with [v2,1/3] drm/i915/gmbus: Switch GMBUS fully to _fw() register accesses (rev2) Patchwork
2026-09-30 16:19 ` ✓ i915.CI.BAT: " Patchwork
2026-09-30 18:11 ` ✓ Xe.CI.FULL: " Patchwork
2026-10-01  6:08 ` ✓ i915.CI.Full: " Patchwork
2026-10-02 14:05 ` ✓ CI.KUnit: success for series starting with [v2,1/3] drm/i915/gmbus: Switch GMBUS fully to _fw() register accesses (rev3) Patchwork
2026-10-02 14:49 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-02 16:18 ` ✗ i915.CI.BAT: failure " Patchwork
2026-10-02 16:26 ` ✗ Xe.CI.FULL: " 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=20260930120137.13C581F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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.