From: Jani Nikula <jani.nikula@intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Subject: RE: [PATCH 00/11] drm/i915: pass dev_priv explicitly to DIP regs
Date: Tue, 28 May 2024 11:11:25 +0300 [thread overview]
Message-ID: <87ttiil5jm.fsf@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6129A87D55BBEE6D3E197417B9F12@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Tue, 28 May 2024, "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Monday, May 27, 2024 4:41 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>
>> Subject: [PATCH 00/11] drm/i915: pass dev_priv explicitly to DIP regs
>>
>> Continue removing implicit dev_priv references.
>>
>
> LGTM
> Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Thanks for the review, pushed to din.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-05-28 8:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 11:10 [PATCH 00/11] drm/i915: pass dev_priv explicitly to DIP regs Jani Nikula
2024-05-27 11:10 ` [PATCH 01/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_CTL Jani Nikula
2024-05-27 11:10 ` [PATCH 02/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_GCP Jani Nikula
2024-05-27 11:10 ` [PATCH 03/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_AVI_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 04/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_VS_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 05/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_SPD_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 06/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_GMP_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 07/11] drm/i915: pass dev_priv explicitly to HSW_TVIDEO_DIP_VSC_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 08/11] drm/i915: pass dev_priv explicitly to GLK_TVIDEO_DIP_DRM_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 09/11] drm/i915: pass dev_priv explicitly to ICL_VIDEO_DIP_PPS_DATA Jani Nikula
2024-05-27 11:10 ` [PATCH 10/11] drm/i915: pass dev_priv explicitly to ICL_VIDEO_DIP_PPS_ECC Jani Nikula
2024-05-27 11:10 ` [PATCH 11/11] drm/i915: pass dev_priv explicitly to ADL_TVIDEO_DIP_AS_SDP_DATA Jani Nikula
2024-05-27 13:59 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: pass dev_priv explicitly to DIP regs Patchwork
2024-05-27 14:07 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-27 23:14 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-28 5:43 ` [PATCH 00/11] " Borah, Chaitanya Kumar
2024-05-28 8:11 ` Jani Nikula [this message]
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=87ttiil5jm.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@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