From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Luca Coelho <luca@coelho.fi>, Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH 0/2] drm/i915/debugfs: intel_display_caps
Date: Thu, 19 Sep 2024 12:48:22 +0300 [thread overview]
Message-ID: <87frpw9dp5.fsf@intel.com> (raw)
In-Reply-To: <cover.1726231866.git.jani.nikula@intel.com>
On Fri, 13 Sep 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> Strike another i915 core -> display include and call.
Thanks for the reviews, pushed to din.
BR,
Jani.
>
> Jani Nikula (2):
> drm/i915/debugfs: remove superfluous kernel_param_lock/unlock
> drm/i915/debugfs: add dedicated intel_display_caps debugfs for display
>
> .../drm/i915/display/intel_display_debugfs.c | 18 ++++++++++++++++++
> drivers/gpu/drm/i915/i915_debugfs.c | 6 ------
> 2 files changed, 18 insertions(+), 6 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-09-19 9:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 12:51 [PATCH 0/2] drm/i915/debugfs: intel_display_caps Jani Nikula
2024-09-13 12:51 ` [PATCH 1/2] drm/i915/debugfs: remove superfluous kernel_param_lock/unlock Jani Nikula
2024-09-13 20:21 ` Andi Shyti
2024-09-13 12:51 ` [PATCH 2/2] drm/i915/debugfs: add dedicated intel_display_caps debugfs for display Jani Nikula
2024-09-19 8:29 ` Luca Coelho
2024-09-13 15:56 ` ✓ CI.Patch_applied: success for drm/i915/debugfs: intel_display_caps Patchwork
2024-09-13 15:56 ` ✓ CI.checkpatch: " Patchwork
2024-09-13 15:59 ` ✓ CI.KUnit: " Patchwork
2024-09-13 16:14 ` ✓ CI.Build: " Patchwork
2024-09-13 16:16 ` ✓ CI.Hooks: " Patchwork
2024-09-13 16:18 ` ✗ CI.checksparse: warning " Patchwork
2024-09-13 16:46 ` ✓ CI.BAT: success " Patchwork
2024-09-14 8:56 ` ✗ CI.FULL: failure " Patchwork
2024-09-19 9:48 ` 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=87frpw9dp5.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=andi.shyti@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox