From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/todo: i915 could use device_link_add
Date: Wed, 21 Feb 2018 00:48:02 +0100 [thread overview]
Message-ID: <20180220234802.GC22199@phenom.ffwll.local> (raw)
In-Reply-To: <20180220141719.naqsr4rwozvkpjn7@ideak-desk.fi.intel.com>
On Tue, Feb 20, 2018 at 04:17:19PM +0200, Imre Deak wrote:
> On Tue, Feb 20, 2018 at 02:20:17PM +0100, Daniel Vetter wrote:
> > Noticed while reading some unrelated patches. Unfortunately Imre's
> > patch to add our early/late hooks predated the device_link
> > infrastructure by 2 years.
> >
> > Cc: Imre Deak <imre.deak@intel.com>
> > Cc: Takashi Iwai <tiwai@suse.de>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>
> Yep, good idea to convert over:
> Acked-by: Imre Deak <imre.deak@intel.com>
Pushed to dinq.
-Daniel
>
> > ---
> > Documentation/gpu/todo.rst | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> > index 1a0a413eeced..f4d0b3476d9c 100644
> > --- a/Documentation/gpu/todo.rst
> > +++ b/Documentation/gpu/todo.rst
> > @@ -450,5 +450,12 @@ See drivers/gpu/drm/amd/display/TODO for tasks.
> >
> > Contact: Harry Wentland, Alex Deucher
> >
> > +i915
> > +----
> > +
> > +- Our early/late pm callbacks could be removed in favour of using
> > + device_link_add to model the dependency between i915 and snd_had. See
> > + https://dri.freedesktop.org/docs/drm/driver-api/device_link.html
> > +
> > Outside DRM
> > ===========
> > --
> > 2.15.1
> >
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-02-20 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 13:20 [PATCH] drm/todo: i915 could use device_link_add Daniel Vetter
2018-02-20 13:40 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-20 14:17 ` [PATCH] " Imre Deak
2018-02-20 23:48 ` Daniel Vetter [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=20180220234802.GC22199@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.de \
/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