From: Oded Gabbay <oded.gabbay@gmail.com>
To: airlied@linux.ie
Cc: dri-devel@lists.freedesktop.org
Subject: [PULL] drm-amdkfd-next-fixes
Date: Tue, 15 Mar 2016 14:13:50 +0200 [thread overview]
Message-ID: <20160315121350.GA14500@odedg-tlv.redhat.com> (raw)
Hi Dave,
Just a small fix for uninitialized variable. Hoping you could squeeze it into
the merge window's pull request, but -rc2 is perfectly fine as well.
Thanks,
Oded
The following changes since commit 211afd577a186e18d3eece543c6767420d6f6737:
Merge tag 'drm-vc4-next-2016-03-14' of github.com:anholt/linux into drm-next (2016-03-15 09:49:19 +1000)
are available in the git repository at:
git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-next-fixes-2016-03-15
for you to fetch changes up to 93fce954427effee89e44a976299b15dd75b4bbc:
drm/amdkfd: uninitialized variable in dbgdev_wave_control_set_registers() (2016-03-15 14:09:37 +0200)
----------------------------------------------------------------
Dan Carpenter (1):
drm/amdkfd: uninitialized variable in dbgdev_wave_control_set_registers()
drivers/gpu/drm/amd/amdkfd/kfd_dbgdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-03-15 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 12:13 Oded Gabbay [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-30 9:47 [PULL] drm-amdkfd-next-fixes Oded Gabbay
2015-08-05 7:05 Oded Gabbay
2015-08-05 7:48 ` Daniel Vetter
2015-08-05 7:49 ` Oded Gabbay
2015-08-05 9:32 ` Daniel Vetter
2015-06-10 12:26 Oded Gabbay
2015-02-03 11:36 Oded Gabbay
2015-01-25 11:21 Oded Gabbay
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=20160315121350.GA14500@odedg-tlv.redhat.com \
--to=oded.gabbay@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@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