From: Ben Skeggs <skeggsb@gmail.com>
To: Lyude Paul <lyude@redhat.com>
Cc: ML nouveau <nouveau@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org,
ML dri-devel <dri-devel@lists.freedesktop.org>,
Karol Herbst <karolherbst@gmail.com>,
Ben Skeggs <bskeggs@redhat.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 0/2] drm/nouveau: CRTC Runtime PM ref tracking fixes
Date: Tue, 13 Aug 2019 14:42:17 +1000 [thread overview]
Message-ID: <CACAvsv760Jtzubm2faimEY1z1tfNPBcsOJg6Ns0wL8W-9fxRXw@mail.gmail.com> (raw)
In-Reply-To: <20190807234709.6076-1-lyude@redhat.com>
On Thu, 8 Aug 2019 at 09:47, Lyude Paul <lyude@redhat.com> wrote:
>
> Just some runtime PM fixes for some much less noticeable runtime PM ref
> tracking issues that I got reminded of when fixing some unrelated issues
> with nouveau.
>
> Changes since v1:
> * Don't fix CRTC RPM code in dispnv04, because it's not actually doing
> anything in the first place. Just get rid of it. - imirkin
>
> Lyude Paul (2):
> drm/nouveau/dispnv04: Remove runtime PM
> drm/nouveau/dispnv50: Fix runtime PM ref tracking for non-blocking
> modesets
>
> drivers/gpu/drm/nouveau/dispnv04/crtc.c | 51 +------------------------
> drivers/gpu/drm/nouveau/dispnv50/disp.c | 38 +++++++++---------
> drivers/gpu/drm/nouveau/nouveau_drv.h | 3 --
> 3 files changed, 18 insertions(+), 74 deletions(-)
For the series: Acked-by: Ben Skeggs <bskeggs@redhat.com>
>
> --
> 2.21.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-13 4:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 23:47 [PATCH v2 0/2] drm/nouveau: CRTC Runtime PM ref tracking fixes Lyude Paul
2019-08-07 23:47 ` [PATCH v2 1/2] drm/nouveau/dispnv04: Remove runtime PM Lyude Paul
2019-08-07 23:47 ` [PATCH v2 2/2] drm/nouveau/dispnv50: Fix runtime PM ref tracking for non-blocking modesets Lyude Paul
2019-08-13 4:42 ` Ben Skeggs [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=CACAvsv760Jtzubm2faimEY1z1tfNPBcsOJg6Ns0wL8W-9fxRXw@mail.gmail.com \
--to=skeggsb@gmail.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karolherbst@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@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;
as well as URLs for NNTP newsgroup(s).