From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for drm/i915/display: move dmc_firmware_path to display params
Date: Thu, 21 Mar 2024 19:35:48 -0000 [thread overview]
Message-ID: <171104974808.941104.7523476827771856198@8e613ede5ea5> (raw)
In-Reply-To: <20240321161856.3517856-1-jani.nikula@intel.com>
== Series Details ==
Series: drm/i915/display: move dmc_firmware_path to display params
URL : https://patchwork.freedesktop.org/series/131442/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
a9eb1ac8298ef9f9146567c29fa762d8e9efa1ef
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 0de0d6418805ddb952e2c1d22d1375d116cc9423
Author: Jani Nikula <jani.nikula@intel.com>
Date: Thu Mar 21 18:18:56 2024 +0200
drm/i915/display: move dmc_firmware_path to display params
The dmc_firmware_path parameter is clearly a display parameter. Move it
there. This also cleans up the ugly member in struct xe_device.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
+ /mt/dim checkpatch ad4a10c6d0e21df4bd830c20c96b795ae2d03962 drm-intel
0de0d6418805 drm/i915/display: move dmc_firmware_path to display params
-:20: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#20: FILE: drivers/gpu/drm/i915/display/intel_display_params.c:31:
+intel_display_param_named_unsafe(dmc_firmware_path, charp, 0400,
+ "DMC firmware path to use instead of the default one");
total: 0 errors, 0 warnings, 1 checks, 66 lines checked
next prev parent reply other threads:[~2024-03-21 19:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:18 [PATCH] drm/i915/display: move dmc_firmware_path to display params Jani Nikula
2024-03-21 16:20 ` Jani Nikula
2024-03-22 4:34 ` Lucas De Marchi
2024-03-22 8:48 ` Jani Nikula
2024-03-22 16:06 ` Lucas De Marchi
2024-03-22 18:32 ` Lucas De Marchi
2024-04-02 8:47 ` Jani Nikula
2024-03-21 19:35 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-21 19:35 ` Patchwork [this message]
2024-03-21 19:36 ` ✓ CI.KUnit: " Patchwork
2024-03-21 19:47 ` ✓ CI.Build: " Patchwork
2024-03-21 19:49 ` ✓ CI.Hooks: " Patchwork
2024-03-21 19:51 ` ✗ CI.checksparse: warning " Patchwork
2024-03-21 20:14 ` ✓ CI.BAT: success " Patchwork
2024-03-21 23:52 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-03-21 23:52 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-03-22 0:02 ` ✗ Fi.CI.BAT: failure " 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=171104974808.941104.7523476827771856198@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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.