From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Dave Airlie <airlied@gmail.com>
Cc: MaliDP Maintainers <malidp@foss.arm.com>,
DRI devel <dri-devel@lists.freedesktop.org>
Subject: [GIT PULL] mali-dp fixes for drm-next
Date: Mon, 23 Jul 2018 15:53:02 +0100 [thread overview]
Message-ID: <20180723145302.GA28052@e110455-lin.cambridge.arm.com> (raw)
Hi Dave,
I have a couple of small patches for malidp to be applied in drm-next.
They have arisen from the decision to switch the writeback connectors to
always connected.
Best regards,
Liviu
The following changes since commit 500775074f88d9cf5416bed2ca19592812d62c41:
Merge branch 'drm-next-4.19' of git://people.freedesktop.org/~agd5f/linux into drm-next (2018-07-20 14:54:31 +1000)
are available in the Git repository at:
git://linux-arm.org/linux-ld.git for-upstream/malidp-fixes
for you to fetch changes up to 2e012e76ad59edb4a5a175c0957a44337dc39d87:
drm: mali-dp: Set encoder possible_clones (2018-07-23 15:42:17 +0100)
----------------------------------------------------------------
Alexandru Gheorghe (2):
drm: mali-dp: Report writeback connector as connected
drm: mali-dp: Set encoder possible_clones
drivers/gpu/drm/arm/malidp_drv.c | 10 ++++++++++
drivers/gpu/drm/arm/malidp_mw.c | 2 +-
2 files changed, 11 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
next reply other threads:[~2018-07-23 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 14:53 Liviu Dudau [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 14:55 [GIT PULL] mali-dp: fixes for drm-next Liviu Dudau
2017-11-24 16:13 Liviu Dudau
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=20180723145302.GA28052@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.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.