Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 0/2] display device info as a separate debugfs entry
Date: Tue, 17 Oct 2023 20:55:41 +0000	[thread overview]
Message-ID: <a0356c4a60b66bb4cc3355aea008723ff6bfd687.camel@intel.com> (raw)
In-Reply-To: <20231017203800.123776-1-vinod.govindapillai@intel.com>

Hi Swati,

Realized that I cannot remove the display runtime info from i915_capabilties until IGT start using
this new created entry.

So excluded the patch to remove the redundant info from i915_capabilties from this series
A new version is sent! Sorry for the confusion!

BR
vinod

On Tue, 2023-10-17 at 23:37 +0300, Vinod Govindapillai wrote:
> Expose the display device info as a separate debugfs entry to list out
> display device info and remove the same from i915_capabilities
> 
> v2: rename the debugs entry to i915_display_capabilities and patch
>     description changes
> 
> Vinod Govindapillai (2):
>   drm/i915/display: debugfs entry to list display capabilities
>   drm/i915: remove display device info from i915 capabilities
> 
>  drivers/gpu/drm/i915/display/intel_display_debugfs.c | 12 ++++++++++++
>  drivers/gpu/drm/i915/i915_debugfs.c                  |  1 -
>  2 files changed, 12 insertions(+), 1 deletion(-)
> 


      parent reply	other threads:[~2023-10-17 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 20:37 [Intel-gfx] [PATCH v2 0/2] display device info as a separate debugfs entry Vinod Govindapillai
2023-10-17 20:37 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/display: debugfs entry to list display capabilities Vinod Govindapillai
2023-10-17 20:38 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: remove display device info from i915 capabilities Vinod Govindapillai
2023-10-17 20:55 ` Govindapillai, Vinod [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=a0356c4a60b66bb4cc3355aea008723ff6bfd687.camel@intel.com \
    --to=vinod.govindapillai@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