From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Ayan Halder <ayan.halder@arm.com>,
MaliDP Maintainers <malidp@foss.arm.com>,
DRI devel <dri-devel@lists.freedesktop.org>
Subject: [GIT PULL] malidp-next-fixes
Date: Fri, 5 Oct 2018 16:24:23 +0100 [thread overview]
Message-ID: <20181005152423.GF1156@e110455-lin.cambridge.arm.com> (raw)
Hi Dave,
I've realised that the commit 3dae1c0919d8 ("drm/arm/malidp: Implemented
the size validation for AFBC framebuffers") got bungled up in the
upstreaming process and it was missing an important line from the
function that calculates the size of the AFBC framebuffer. The patch to
fix it has now been added into my repo, please pull into drm-next when
convenient.
Many thanks,
Liviu
The following changes since commit c530174b90fa3bcaa83d168b001b574bcb2da021:
Merge branch 'for-upstream/mali-dp' of git://linux-arm.org/linux-ld into drm-next (2018-10-04 11:31:05 +1000)
are available in the Git repository at:
git://linux-arm.org/linux-ld.git for-upstream/mali-dp
for you to fetch changes up to fd99bd8b805c7c01af7dd66e22bb31c8cfe64310:
drm: malidp: Add the size of the superblocks when calculating total size for AFBC buffers (2018-10-05 15:39:51 +0100)
----------------------------------------------------------------
Liviu Dudau (1):
drm: malidp: Add the size of the superblocks when calculating total size for AFBC buffers
drivers/gpu/drm/arm/malidp_drv.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-10-05 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181005152423.GF1156@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.com \
--cc=ayan.halder@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=malidp@foss.arm.com \
/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.