From: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
daniel.vetter-/w4YWyX8dFk@public.gmane.org
Cc: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>
Subject: [pull] amdgpu drm-fixes-5.4
Date: Wed, 9 Oct 2019 22:10:23 -0500 [thread overview]
Message-ID: <20191010031023.23359-1-alexander.deucher@amd.com> (raw)
Hi Dave, Daniel,
Just a single fix this week for 5.4.
The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:
Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)
are available in the Git repository at:
git://people.freedesktop.org/~agd5f/linux tags/drm-fixes-5.4-2019-10-09
for you to fetch changes up to 083164dbdb17c5ea4ad92c1782b59c9d75567790:
drm/amdgpu: fix memory leak (2019-10-09 11:45:59 -0500)
----------------------------------------------------------------
drm-fixes-5.4-2019-10-09:
amdgpu:
- fix memory leak in bo_list ioctl error path
----------------------------------------------------------------
Nirmoy Das (1):
drm/amdgpu: fix memory leak
drivers/gpu/drm/amd/amdgpu/amdgpu_bo_list.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2019-10-10 3:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 3:10 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-20 23:51 [pull] amdgpu drm-fixes-5.4 Alex Deucher
2019-11-20 23:51 ` Alex Deucher
2019-11-14 22:13 Alex Deucher
2019-11-14 22:13 ` Alex Deucher
2019-10-24 3:18 Alex Deucher
2019-10-24 3:18 ` Alex Deucher
2019-10-24 3:18 ` Alex Deucher
2019-10-02 20:49 Alex Deucher
2019-09-25 21:35 Alex Deucher
2019-09-19 15:38 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=20191010031023.23359-1-alexander.deucher@amd.com \
--to=alexdeucher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=alexander.deucher-5C7GfCeVMHo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.