From: "Michel Dänzer" <michel@daenzer.net>
To: Flora Cui <Flora.Cui@amd.com>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH libdrm] amdgpu: update the exported always on CU bitmap
Date: Mon, 26 Jun 2017 15:52:48 +0900 [thread overview]
Message-ID: <1279398b-b8ca-5de3-e171-1fdec97322f3@daenzer.net> (raw)
In-Reply-To: <1498457550-27605-1-git-send-email-Flora.Cui@amd.com>
On 26/06/17 03:12 PM, Flora Cui wrote:
> keep cu_ao_mask unchanged for backward compatibility.
>
> Change-Id: I9f497aadd309977468e246fea333b392c0150276
> Signed-off-by: Flora Cui <Flora.Cui@amd.com>
> ---
> This patch should be landed after the kmd patch upsteam. right?
Right. Also, include/drm/amdgpu_drm.h should be updated in a separate
patch, see include/drm/README (in particular the "When and how to
update these files").
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-06-26 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1497946521-21500-1-git-send-email-Flora.Cui@amd.com>
[not found] ` <1497946521-21500-1-git-send-email-Flora.Cui-5C7GfCeVMHo@public.gmane.org>
2017-06-20 9:04 ` [PATCH libdrm] amdgpu: update always on cu bitmap Flora Cui
[not found] ` <1497949479-22146-1-git-send-email-Flora.Cui-5C7GfCeVMHo@public.gmane.org>
2017-06-20 9:49 ` Christian König
[not found] ` <75494a7b-0ee1-b8e4-9b5e-a82bfeb0d1bb-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-06-20 10:13 ` Daniel Vetter
2017-06-21 2:13 ` Flora Cui
2017-06-21 7:08 ` Daniel Vetter
2017-06-26 6:12 ` [PATCH libdrm] amdgpu: update the exported always on CU bitmap Flora Cui
2017-06-26 6:52 ` Michel Dänzer [this message]
[not found] ` <1498457550-27605-1-git-send-email-Flora.Cui-5C7GfCeVMHo@public.gmane.org>
2017-06-26 7:15 ` Christian König
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=1279398b-b8ca-5de3-e171-1fdec97322f3@daenzer.net \
--to=michel@daenzer.net \
--cc=Flora.Cui@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).