dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sean Paul <seanpaul@chromium.org>
Cc: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>,
	Emil Velikov <emil.l.velikov@gmail.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 00/21] drm: make fbdev support really optional
Date: Mon, 18 Jul 2016 09:13:14 +0200	[thread overview]
Message-ID: <20160718071314.GW17101@phenom.ffwll.local> (raw)
In-Reply-To: <CAOw6vb+_gKAjLPuAqz2-qYZ=Z9kfaF8bVBcdZccpX6PY0AAL=Q@mail.gmail.com>

On Fri, Jul 15, 2016 at 10:37:45AM -0400, Sean Paul wrote:
> On Fri, Jul 15, 2016 at 10:17 AM, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> > On 15 July 2016 at 14:37, Tobias Jakobi <tjakobi@math.uni-bielefeld.de> wrote:
> >> Hello Emil,
> >>
> >> Emil Velikov wrote:
> >>> On 15 July 2016 at 13:47, Tobias Jakobi <tjakobi@math.uni-bielefeld.de> wrote:
> >>>> Hello,
> >>>>
> >>>> as request by Daniel here (http://www.spinics.net/lists/dri-devel/msg112592.html) I went ahead and also cleaned up the other Kconfig files. I have mostly compile tested the changes on an ARMv7 system (COMPILE_TEST).
> >>>>
> >>> Yay :-) IIRC some drivers don't fully use the fb_helpers (for example
> >>> vmwgfx still references the cfb_* API), so they should be updated as
> >>> well.
> >> I can only do this on ARM atm, so I suggest to just drop insufficient
> >> patches.
> >>
> > Without checking (build and/or grep) it'll be a bit hard to figure out
> > which patches are insufficient. At the end of the day it's up-to you
> > and DRM maintainer(s).
> >
> 
> I've compile tested atmel/nouveau/rcar/rockchip, I'll merge those in drm-misc.
> 
> Since I can't test the others easily, I'll leave them for now.

vmwgfx seems to be the only special case (it doesn't use any of the kms
helpers at all, so that's normal). I merged all the others.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-07-18  7:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 12:47 [PATCH 00/21] drm: make fbdev support really optional Tobias Jakobi
2016-07-15 12:47 ` [PATCH 01/21] drm/arc: " Tobias Jakobi
2016-07-15 12:47 ` [PATCH 02/21] drm/armada: " Tobias Jakobi
2016-07-15 12:47 ` [PATCH 03/21] drm/omap: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 04/21] drm/mgag200: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 05/21] drm/cirrus: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 06/21] drm/qxl: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 07/21] drm/imx: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 08/21] drm/shmobile: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 09/21] drm/rockchip: " Tobias Jakobi
2016-07-15 15:01   ` Sean Paul
2016-07-15 12:48 ` [PATCH 10/21] drm/gma500: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 11/21] drm/rcar-du: " Tobias Jakobi
2016-07-15 15:01   ` Sean Paul
2016-07-15 12:48 ` [PATCH 12/21] drm/tilcdc: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 13/21] drm/fsl-dcu: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 14/21] drm/bochs: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 15/21] drm/vmwgfx: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 16/21] drm/udl: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 17/21] drm/atmel-hlcdc: " Tobias Jakobi
2016-07-15 15:01   ` Sean Paul
2016-07-15 12:48 ` [PATCH 18/21] drm/virtio: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 19/21] drm/ast: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 20/21] drm/arm: " Tobias Jakobi
2016-07-15 12:48 ` [PATCH 21/21] drm/nouveau: " Tobias Jakobi
2016-07-15 15:01   ` Sean Paul
2016-07-15 13:21 ` [PATCH 00/21] drm: " Emil Velikov
2016-07-15 13:37   ` Tobias Jakobi
2016-07-15 14:17     ` Emil Velikov
2016-07-15 14:37       ` Sean Paul
2016-07-18  7:13         ` Daniel Vetter [this message]
2016-07-15 14:47       ` Tobias Jakobi

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=20160718071314.GW17101@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=seanpaul@chromium.org \
    --cc=tjakobi@math.uni-bielefeld.de \
    /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