From: Sean Paul <sean@poorly.run>
To: Dave Airlie <airlied@gmail.com>
Cc: dim-tools@lists.freedesktop.org,
Neil Armstrong <narmstrong@baylibre.com>,
intel-gfx@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Sean Paul <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PULL] drm-misc-next-fixes for 4.20
Date: Wed, 3 Oct 2018 15:59:57 -0400 [thread overview]
Message-ID: <20181003195957.GA64584@art_vandelay> (raw)
Hi Dave,
We've cut over to misc-next-fixes for 4.20, so just one patch this week. It's
Neil's fix for mali binary driver.
drm-misc-next-fixes-2018-10-03:
- Add EXPERT config option to allow phys mem leak from fbdev for blob drivers (Neil)
Cc: Neil Armstrong <narmstrong@baylibre.com>
Cheers, Sean
The following changes since commit 87c2ee740c07f1edae9eec8bc45cb9b32a68f323:
Merge branch 'drm-next-4.20' of git://people.freedesktop.org/~agd5f/linux into drm-next (2018-09-28 09:48:40 +1000)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-fixes-2018-10-03
for you to fetch changes up to 4be9bd10e22dfc7fc101c5cf5969ef2d3a042d8a:
drm/fb_helper: Allow leaking fbdev smem_start (2018-10-03 21:08:21 +0200)
----------------------------------------------------------------
- Add EXPERT config option to allow phys mem leak from fbdev for blob drivers (Neil)
Cc: Neil Armstrong <narmstrong@baylibre.com>
----------------------------------------------------------------
Neil Armstrong (1):
drm/fb_helper: Allow leaking fbdev smem_start
drivers/gpu/drm/Kconfig | 20 ++++++++++++++++++++
drivers/gpu/drm/drm_fb_helper.c | 33 +++++++++++++++++++++++++++++++--
2 files changed, 51 insertions(+), 2 deletions(-)
--
Sean Paul, Software Engineer, Google / Chromium OS
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-10-03 19:59 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=20181003195957.GA64584@art_vandelay \
--to=sean@poorly.run \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=narmstrong@baylibre.com \
--cc=rodrigo.vivi@intel.com \
--cc=seanpaul@chromium.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