From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/todo: Add entry to remove load/unload hooks
Date: Thu, 24 Oct 2019 12:35:52 +0200 [thread overview]
Message-ID: <20191024103552.GB2825247@ulmo> (raw)
In-Reply-To: <20191023144953.28190-2-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 769 bytes --]
On Wed, Oct 23, 2019 at 04:49:53PM +0200, Daniel Vetter wrote:
> They're midlayer, broken, and because of the old gunk, we can't fix
> them. For examples see the various checks in drm_mode_object.c against
> dev->registered, which cannot be enforced if the driver still uses the
> load hook.
>
> Unfortunately our biggest driver still uses load/unload, so this would
> be really great to get fixed.
>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> Documentation/gpu/todo.rst | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
Reminds me that I need to still do that for Tegra:
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Harry Wentland <harry.wentland@amd.com>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/todo: Add entry to remove load/unload hooks
Date: Thu, 24 Oct 2019 12:35:52 +0200 [thread overview]
Message-ID: <20191024103552.GB2825247@ulmo> (raw)
Message-ID: <20191024103552.ONEFUqnUjtVvJwHceRtMqXCATMtqpUYe8b6kGBME374@z> (raw)
In-Reply-To: <20191023144953.28190-2-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 769 bytes --]
On Wed, Oct 23, 2019 at 04:49:53PM +0200, Daniel Vetter wrote:
> They're midlayer, broken, and because of the old gunk, we can't fix
> them. For examples see the various checks in drm_mode_object.c against
> dev->registered, which cannot be enforced if the driver still uses the
> load hook.
>
> Unfortunately our biggest driver still uses load/unload, so this would
> be really great to get fixed.
>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> Documentation/gpu/todo.rst | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
Reminds me that I need to still do that for Tegra:
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-24 10:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 14:49 [PATCH 1/2] drm/property: Enforce more lifetime rules Daniel Vetter
2019-10-23 14:49 ` [Intel-gfx] " Daniel Vetter
2019-10-23 14:49 ` [PATCH 2/2] drm/todo: Add entry to remove load/unload hooks Daniel Vetter
2019-10-23 14:49 ` [Intel-gfx] " Daniel Vetter
2019-10-24 10:35 ` Thierry Reding [this message]
2019-10-24 10:35 ` Thierry Reding
2019-11-04 16:57 ` Daniel Vetter
2019-11-04 16:57 ` Daniel Vetter
2019-10-24 0:46 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/property: Enforce more lifetime rules Patchwork
2019-10-24 0:46 ` [Intel-gfx] " Patchwork
2019-10-24 1:14 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-24 1:14 ` [Intel-gfx] " Patchwork
2019-10-24 10:40 ` [PATCH 1/2] " Thierry Reding
2019-10-24 10:40 ` [Intel-gfx] " Thierry Reding
2019-10-24 10:43 ` Thierry Reding
2019-10-24 10:43 ` [Intel-gfx] " Thierry Reding
2019-10-24 11:47 ` Daniel Vetter
2019-10-24 11:47 ` Daniel Vetter
2019-10-24 12:09 ` Jani Nikula
2019-10-24 12:09 ` [Intel-gfx] " Jani Nikula
2019-10-24 22:35 ` ✗ Fi.CI.IGT: failure for series starting with [1/2] " Patchwork
2019-10-24 22:35 ` [Intel-gfx] " 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=20191024103552.GB2825247@ulmo \
--to=thierry.reding@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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