From: Jani Nikula <jani.nikula@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915/backlight: convert to use struct intel_display
Date: Wed, 05 Feb 2025 20:06:55 +0200 [thread overview]
Message-ID: <87r04c2rls.fsf@intel.com> (raw)
In-Reply-To: <SN7PR11MB67508B47B517EA6DD93BE4CFE3F72@SN7PR11MB6750.namprd11.prod.outlook.com>
On Wed, 05 Feb 2025, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: Tuesday, February 4, 2025 6:54 PM
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>
>> Subject: [PATCH] drm/i915/backlight: convert to use struct intel_display
>>
>> Going forward, struct intel_display will be the main display data
>> structure. Convert as much as possible of backlight code to use it.
>>
>> There are some stragglers mainly around PCH checks.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> LGTM,
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
Thanks for the review, pushed to din.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-02-05 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:24 [PATCH] drm/i915/backlight: convert to use struct intel_display Jani Nikula
2025-02-04 16:11 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-04 16:11 ` ✓ CI.checkpatch: " Patchwork
2025-02-04 16:12 ` ✓ CI.KUnit: " Patchwork
2025-02-04 16:29 ` ✓ CI.Build: " Patchwork
2025-02-04 16:31 ` ✓ CI.Hooks: " Patchwork
2025-02-04 16:33 ` ✓ CI.checksparse: " Patchwork
2025-02-04 16:52 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-04 19:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-05 9:11 ` [PATCH] " Kandpal, Suraj
2025-02-05 18:06 ` 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=87r04c2rls.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox