Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	Gustavo Sousa <gustavo.sousa@intel.com>
Subject: Re: [PATCH v2 0/5] drm/i915/dmc: firmware path handling changes
Date: Mon, 22 Apr 2024 18:04:33 +0300	[thread overview]
Message-ID: <87zftlsake.fsf@intel.com> (raw)
In-Reply-To: <xa6zj5rxk725th4em7knyei2745fpps5bplqsdft7ua3one7oo@ufm4kw24rj3i>

On Fri, 19 Apr 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Apr 19, 2024 at 12:41:53PM GMT, Jani Nikula wrote:
>>v2 of https://lore.kernel.org/r/cover.1713450693.git.jani.nikula@intel.com
>>
>>Jani Nikula (5):
>>  drm/i915/dmc: handle request_firmware() errors separately
>>  drm/i915/dmc: improve firmware parse failure propagation
>>  drm/i915/dmc: split out per-platform firmware path selection
>>  drm/i915/dmc: change how to disable DMC firmware using module param
>>  drm/i915/display: move dmc_firmware_path to display params
>>
>> .../drm/i915/display/intel_display_params.c   |   4 +
>> .../drm/i915/display/intel_display_params.h   |   1 +
>> drivers/gpu/drm/i915/display/intel_dmc.c      | 175 +++++++++++-------
>> drivers/gpu/drm/i915/i915_params.c            |   3 -
>> drivers/gpu/drm/i915/i915_params.h            |   1 -
>> drivers/gpu/drm/xe/xe_device_types.h          |   3 -
>
> Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>

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

BR,
Jani.



>
> thanks
> Lucas De Marchi
>
>> 6 files changed, 112 insertions(+), 75 deletions(-)
>>
>>-- 
>>2.39.2
>>

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-04-22 15:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  9:41 [PATCH v2 0/5] drm/i915/dmc: firmware path handling changes Jani Nikula
2024-04-19  9:41 ` [PATCH v2 1/5] drm/i915/dmc: handle request_firmware() errors separately Jani Nikula
2024-04-19  9:41 ` [PATCH v2 2/5] drm/i915/dmc: improve firmware parse failure propagation Jani Nikula
2024-04-19  9:41 ` [PATCH v2 3/5] drm/i915/dmc: split out per-platform firmware path selection Jani Nikula
2024-04-19  9:41 ` [PATCH v2 4/5] drm/i915/dmc: change how to disable DMC firmware using module param Jani Nikula
2024-04-19 12:32   ` Gustavo Sousa
2024-04-19  9:41 ` [PATCH v2 5/5] drm/i915/display: move dmc_firmware_path to display params Jani Nikula
2024-04-19 10:29 ` ✓ CI.Patch_applied: success for drm/i915/dmc: firmware path handling changes (rev2) Patchwork
2024-04-19 10:29 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-19 10:30 ` ✓ CI.KUnit: success " Patchwork
2024-04-19 10:41 ` ✓ CI.Build: " Patchwork
2024-04-19 10:44 ` ✓ CI.Hooks: " Patchwork
2024-04-19 10:46 ` ✗ CI.checksparse: warning " Patchwork
2024-04-19 11:17 ` ✓ CI.BAT: success " Patchwork
2024-04-19 16:08 ` [PATCH v2 0/5] drm/i915/dmc: firmware path handling changes Lucas De Marchi
2024-04-22 15:04   ` Jani Nikula [this message]
2024-04-21  3:26 ` ✗ CI.FULL: failure for drm/i915/dmc: firmware path handling changes (rev2) 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=87zftlsake.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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