From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Stone <daniels@collabora.com>
Cc: Thierry Reding <treding@nvidia.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/gma500: Fix Medfield for drm_framebuffer move
Date: Tue, 22 May 2018 11:19:49 +0200 [thread overview]
Message-ID: <20180522091949.GA1327@ulmo> (raw)
In-Reply-To: <20180521142449.20800-1-daniels@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 968 bytes --]
On Mon, May 21, 2018 at 03:24:49PM +0100, Daniel Stone wrote:
> bc61c97502e2 moved the gtt_range structure, from being in
> psb_framebuffer and embedding the GEM object, to being placed in the
> drm_framebuffer with the gtt_range being derived from the GEM object.
>
> The conversion missed out the Medfield subdriver, which was not being
> built in the default drm-misc config. Do the trivial fixup here.
>
> Signed-off-by: Daniel Stone <daniels@collabora.com>
> Reported-by: kbuild test robot <lkp@intel.com>
> Fixes: bc61c97502e2 ("drm/gma500: Move GEM BO to drm_framebuffer")
> Cc: Thierry Reding <treding@nvidia.com>
> Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
> ---
> drivers/gpu/drm/gma500/mdfld_intel_display.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Can you send a patch to enable the Medfield subdriver in the drm-misc
default configuration?
This patch:
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-22 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 14:24 [PATCH] drm/gma500: Fix Medfield for drm_framebuffer move Daniel Stone
2018-05-22 9:19 ` Thierry Reding [this message]
2018-05-22 9:24 ` Daniel Stone
2018-05-22 9:31 ` Thierry Reding
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=20180522091949.GA1327@ulmo \
--to=thierry.reding@gmail.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox