All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Luca Coelho <luca@coelho.fi>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/i915/wm: move struct intel_watermark_params to i9xx_wm.c
Date: Thu, 05 Sep 2024 12:58:39 +0300	[thread overview]
Message-ID: <87bk12qv5c.fsf@intel.com> (raw)
In-Reply-To: <d1fb6ed8e3808f3d7daa19f5eb5fa46fb697d0ab.camel@coelho.fi>

On Thu, 05 Sep 2024, Luca Coelho <luca@coelho.fi> wrote:
> On Mon, 2024-08-26 at 19:31 +0300, Jani Nikula wrote:
>> The definition is only used within i9xx_wm.c, hide it there.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>
> Reviewed-by: Luca Coelho <luciano.coelho@intel.com>

Thanks for the reviews, pushed the lot to drm-intel-next.

BR,
Jani.


-- 
Jani Nikula, Intel

  parent reply	other threads:[~2024-09-05  9:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 16:31 [PATCH 0/7] drm/i915/display: intel_display_types.h cleanup Jani Nikula
2024-08-26 16:31 ` [PATCH 1/7] drm/i915/wm: move struct intel_watermark_params to i9xx_wm.c Jani Nikula
     [not found]   ` <d1fb6ed8e3808f3d7daa19f5eb5fa46fb697d0ab.camel@coelho.fi>
2024-09-05  9:58     ` Jani Nikula [this message]
2024-08-26 16:31 ` [PATCH 2/7] drm/i915/hdcp: split out intel_hdcp_shim.h for struct intel_hdcp_shim Jani Nikula
2024-08-26 16:31 ` [PATCH 3/7] drm/i915/display: include drm/drm_probe_helper.h where needed Jani Nikula
2024-08-26 16:31 ` [PATCH 4/7] drm/i915/display: include drm/drm_vblank.h " Jani Nikula
2024-08-26 16:31 ` [PATCH 5/7] drm/i915/display: include media/cec-notifier.h and linux/debugfs.h " Jani Nikula
2024-08-27 10:27   ` kernel test robot
2024-08-27 10:45   ` [PATCH v2] " Jani Nikula
2024-08-27 19:28   ` [PATCH 5/7] " kernel test robot
2024-08-26 16:31 ` [PATCH 6/7] drm/i915/fb: hide the guts of intel_fb_obj() Jani Nikula
2024-08-26 16:31 ` [PATCH 7/7] drm/i915/display: drop extra includes from intel_display_types.h Jani Nikula
2024-08-26 16:37 ` ✓ CI.Patch_applied: success for drm/i915/display: intel_display_types.h cleanup Patchwork
2024-08-26 16:38 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-26 16:39 ` ✓ CI.KUnit: success " Patchwork
2024-08-26 16:51 ` ✓ CI.Build: " Patchwork
2024-08-26 16:53 ` ✗ CI.Hooks: failure " Patchwork
2024-08-26 16:54 ` ✗ CI.checksparse: warning " Patchwork
2024-08-26 17:14 ` ✓ CI.BAT: success " Patchwork
2024-08-26 19:12 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-08-26 19:12 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-08-26 19:22 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-26 21:24 ` ✗ CI.FULL: " Patchwork
2024-08-27 10:51 ` ✓ CI.Patch_applied: success for drm/i915/display: intel_display_types.h cleanup (rev2) Patchwork
2024-08-27 10:51 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-27 10:52 ` ✓ CI.KUnit: success " Patchwork
2024-08-27 11:04 ` ✓ CI.Build: " Patchwork
2024-08-27 11:06 ` ✓ CI.Hooks: " Patchwork
2024-08-27 11:08 ` ✗ CI.checksparse: warning " Patchwork
2024-08-27 11:27 ` ✓ CI.BAT: success " Patchwork
2024-08-27 12:41 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-08-27 12:41 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-08-27 12:49 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-27 18:36 ` ✗ CI.FULL: failure " Patchwork
2024-08-28  7:15 ` ✗ Fi.CI.IGT: " 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=87bk12qv5c.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=luca@coelho.fi \
    /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.