From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: quic_jhugo@quicinc.com, dri-devel@lists.freedesktop.org,
ogabbay@kernel.org, mcanal@igalia.com, mwen@igalia.com,
maxime@cerno.tech, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, wambui.karugax@gmail.com
Subject: Re: [Intel-gfx] DRM debugfs cleanup take 3
Date: Wed, 22 Mar 2023 12:20:03 +0100 [thread overview]
Message-ID: <20230322112003.GB2066233@linux.intel.com> (raw)
In-Reply-To: <20230316082035.567520-1-christian.koenig@amd.com>
On Thu, Mar 16, 2023 at 09:20:28AM +0100, Christian König wrote:
> Hi guys,
>
> I've messed up the last send out. Cleanup up some issues reported by people with the accel drivers (duplicated files) and rebased the result.
>
> Apart from that the same approach we already discussed previously.
I tested the whole set with accel/ivpu driver and everything works as expected.
Regards
Stanislaw
prev parent reply other threads:[~2023-03-22 11:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 8:20 [Intel-gfx] DRM debugfs cleanup take 3 Christian König
2023-03-16 8:20 ` [Intel-gfx] [PATCH 1/7] drm: remove drm_dev_set_unique Christian König
2023-03-16 14:15 ` Jeffrey Hugo
2023-03-16 8:20 ` [Intel-gfx] [PATCH 2/7] drm/tegra: allow compile test on !ARM Christian König
2023-03-16 22:58 ` kernel test robot
2023-03-16 8:20 ` [Intel-gfx] [PATCH 3/7] drm/debugfs: stop calling debugfs_init() for the render node Christian König
2023-03-16 8:20 ` [Intel-gfx] [PATCH 4/7] drm/debugfs: rework debugfs directory creation v2 Christian König
2023-03-16 22:27 ` kernel test robot
2023-03-22 11:17 ` Stanislaw Gruszka
2023-03-16 8:20 ` [Intel-gfx] [PATCH 5/7] drm/debugfs: remove dev->debugfs_list and debugfs_mutex v2 Christian König
2023-03-16 8:20 ` [Intel-gfx] [PATCH 6/7] drm/debugfs: rework drm_debugfs_create_files implementation Christian König
2023-03-16 8:20 ` [Intel-gfx] [PATCH 7/7] drm/debugfs: remove debugfs_root pointer from minor Christian König
2023-03-16 11:24 ` kernel test robot
2023-03-16 8:25 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/7] drm: remove drm_dev_set_unique Patchwork
2023-03-22 11:58 ` Jani Nikula
2023-03-22 13:51 ` Christian König
2023-03-22 11:20 ` Stanislaw Gruszka [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=20230322112003.GB2066233@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=mcanal@igalia.com \
--cc=mwen@igalia.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=wambui.karugax@gmail.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