From: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
To: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>,
daniel.vetter-/w4YWyX8dFk@public.gmane.org,
airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [pull] amdgpu drm-fixes-5.2
Date: Fri, 14 Jun 2019 17:49:09 +0200 [thread overview]
Message-ID: <20190614154909.GD23020@phenom.ffwll.local> (raw)
In-Reply-To: <20190613021856.3307-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
On Wed, Jun 12, 2019 at 09:18:56PM -0500, Alex Deucher wrote:
> Hi Dave, Daniel,
>
> Fixes for 5.2:
> - Extend previous vce fix for resume to uvd and vcn
> - Fix bounds checking in ras debugfs interface
> - Fix a regression on SI using amdgpu
>
> The following changes since commit 671e2ee5ee2127179ca884b439ab6001a623edd6:
>
> Merge branch 'linux-5.2' of git://github.com/skeggsb/linux into drm-fixes (2019-06-07 17:16:00 +1000)
Somehow missed this one, but just found it before I wanted to push out the
-fixes pull to Linus ...
> are available in the Git repository at:
>
> git://people.freedesktop.org/~agd5f/linux drm-fixes-5.2
Pulled, thanks.
-Daniel
>
> for you to fetch changes up to f3a5231c8f14acd42845e9e60f506b4e948f0e68:
>
> drm/amdgpu: return 0 by default in amdgpu_pm_load_smu_firmware (2019-06-12 20:39:49 -0500)
>
> ----------------------------------------------------------------
> Alex Deucher (1):
> drm/amdgpu: return 0 by default in amdgpu_pm_load_smu_firmware
>
> Dan Carpenter (1):
> drm/amdgpu: Fix bounds checking in amdgpu_ras_is_supported()
>
> Shirish S (1):
> drm/amdgpu/{uvd,vcn}: fetch ring's read_ptr after alloc
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_pm.c | 4 ++--
> drivers/gpu/drm/amd/amdgpu/amdgpu_ras.h | 2 ++
> drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 4 +++-
> drivers/gpu/drm/amd/amdgpu/uvd_v6_0.c | 5 ++++-
> drivers/gpu/drm/amd/amdgpu/uvd_v7_0.c | 5 ++++-
> 5 files changed, 15 insertions(+), 5 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2019-06-14 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 2:18 [pull] amdgpu drm-fixes-5.2 Alex Deucher
[not found] ` <20190613021856.3307-1-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2019-06-14 15:49 ` Daniel Vetter [this message]
2019-06-14 15:56 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2019-07-03 1:57 Alex Deucher
2019-07-03 9:54 ` Daniel Vetter
[not found] ` <20190703095453.GE15868-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2019-07-03 13:10 ` Alex Deucher
[not found] ` <CADnq5_PC44xY9S3C+s0D4Yx9e3Wsh7TM_-yqe1auRDMWgBZ49g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-07-03 13:20 ` Daniel Vetter
2019-06-05 18:23 Alex Deucher
2019-05-29 17:03 Alex Deucher
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=20190614154909.GD23020@phenom.ffwll.local \
--to=daniel-/w4ywyx8dfk@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
--cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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