From: Gustavo Padovan <gustavo@padovan.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 07/15] drm/gma500: Nuke device_is_agp callback
Date: Wed, 25 Jan 2017 10:58:02 -0200 [thread overview]
Message-ID: <20170125125802.GE2586@joana> (raw)
In-Reply-To: <20170125062657.19270-8-daniel.vetter@ffwll.ch>
Hi Daniel,
2017-01-25 Daniel Vetter <daniel.vetter@ffwll.ch>:
> Returning 0 for an on-chip gpu doesn't change anything at all.
>
> Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> drivers/gpu/drm/gma500/psb_drv.c | 6 ------
> 1 file changed, 6 deletions(-)
Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-25 12:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 6:26 [PATCH 00/15] More kerneldoc cleanup Daniel Vetter
2017-01-25 6:26 ` [PATCH 01/15] drm/kms-helpers: Use recommened kerneldoc for struct member refs Daniel Vetter
2017-01-25 12:48 ` [Intel-gfx] " Gustavo Padovan
2017-01-25 15:19 ` Daniel Vetter
2017-01-25 6:26 ` [PATCH 02/15] drm/bridge: " Daniel Vetter
2017-01-25 9:33 ` Archit Taneja
2017-01-25 12:40 ` Daniel Vetter
2017-01-25 6:26 ` [PATCH 03/15] drm/kms-core: " Daniel Vetter
2017-01-25 13:52 ` Eric Engestrom
2017-01-25 6:26 ` [PATCH 04/15] drm/gem|prime|mm: " Daniel Vetter
2017-01-25 12:51 ` Gustavo Padovan
2017-01-25 6:26 ` [PATCH 05/15] drm/core: " Daniel Vetter
2017-01-25 12:55 ` Gustavo Padovan
2017-01-25 15:23 ` Daniel Vetter
2017-01-25 6:26 ` [PATCH 06/15] drm/doc: Clarify connector overview Daniel Vetter
2017-01-25 12:57 ` [Intel-gfx] " Gustavo Padovan
2017-01-25 15:33 ` Daniel Vetter
2017-01-25 18:08 ` Gustavo Padovan
2017-01-25 6:26 ` [PATCH 07/15] drm/gma500: Nuke device_is_agp callback Daniel Vetter
2017-01-25 12:58 ` Gustavo Padovan [this message]
2017-01-26 0:11 ` Patrik Jakobsson
2017-01-25 6:26 ` [PATCH 08/15] drm/i810: drop " Daniel Vetter
2017-01-25 17:36 ` Alex Deucher
2017-01-25 6:26 ` [PATCH 09/15] drm/mga: remove " Daniel Vetter
2017-01-25 17:33 ` Alex Deucher
2017-01-25 6:26 ` [PATCH 10/15] drm: " Daniel Vetter
2017-01-25 17:34 ` Alex Deucher
2017-01-25 6:26 ` [PATCH 11/15] drm: Nuke ums vgaarb support Daniel Vetter
2017-01-25 17:40 ` Alex Deucher
2017-01-25 6:26 ` [PATCH 12/15] drm/moc: Mark legacy fields in drm_driver as such Daniel Vetter
2017-01-25 17:43 ` Alex Deucher
2017-01-25 6:26 ` [PATCH 13/15] drm/doc: Fix typos for early_unregister doc Daniel Vetter
2017-01-26 9:49 ` Daniel Vetter
2017-01-25 6:26 ` [PATCH 14/15] drm: s/drm_crtc_get_hv_timings/drm_mode_get_hv_timings/ Daniel Vetter
2017-01-25 17:31 ` Alex Deucher
2017-01-26 9:48 ` Daniel Vetter
2017-01-25 6:26 ` [PATCH 15/15] drm: Update kerneldoc for drm_crtc.[hc] Daniel Vetter
2017-01-25 14:26 ` Eric Engestrom
2017-01-25 15:36 ` Daniel Vetter
2017-01-25 7:54 ` ✗ Fi.CI.BAT: warning for More kerneldoc cleanup Patchwork
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=20170125125802.GE2586@joana \
--to=gustavo@padovan.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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).