dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2
Date: Tue, 16 May 2023 12:59:29 +0200	[thread overview]
Message-ID: <20230516105929.GA492258@linux.intel.com> (raw)
In-Reply-To: <20230424123028.25986-1-christian.koenig@amd.com>

On Mon, Apr 24, 2023 at 02:30:24PM +0200, Christian König wrote:
> We want to remove per minor debugfs directories. Start by stopping
> drivers from adding anything inside of those in the mid layer callback.
> 
> v2: drop it for the accel node as well
> 
> Signed-off-by: Christian König <christian.koenig@amd.com>
Tested-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>

I tested with accel and ivpu driver.

I believe main concern of prevent access before registering
is already solved. Any plans to apply this ? 

Regards
Stanislaw


  parent reply	other threads:[~2023-05-16 10:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 12:30 [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2 Christian König
2023-04-24 12:30 ` [PATCH 2/5] drm/debugfs: disallow debugfs access when device isn't registered Christian König
2023-04-24 12:30 ` [PATCH 3/5] drm/debugfs: rework debugfs directory creation v4 Christian König
2023-04-24 12:30 ` [PATCH 4/5] drm/debugfs: remove dev->debugfs_list and debugfs_mutex v2 Christian König
2023-04-24 12:30 ` [PATCH 5/5] drm/debugfs: rework drm_debugfs_create_files implementation Christian König
2023-05-16 10:59 ` Stanislaw Gruszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-29 11:01 DRM debugfs cleanup take 6 Christian König
2023-08-29 11:01 ` [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2 Christian König
2023-08-30  8:19   ` Andi Shyti
2023-08-30 14:22     ` Christian König
2023-09-01  8:00   ` Tomer Tayar
2023-07-11 14:04 DRM debugfs cleanup take 5 (resend) Christian König
2023-07-11 14:04 ` [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2 Christian König
2023-04-12 14:52 DRM debugfs cleanup take 4 Christian König
2023-04-12 14:52 ` [PATCH 1/5] drm/debugfs: drop debugfs_init() for the render and accel node v2 Christian König

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=20230516105929.GA492258@linux.intel.com \
    --to=stanislaw.gruszka@linux.intel.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@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