dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] drm/vgem: Fix vgem_init to get drm device avaliable.
Date: Thu, 29 Mar 2018 09:17:04 +0200	[thread overview]
Message-ID: <20180329071704.GF3881@phenom.ffwll.local> (raw)
In-Reply-To: <CACvgo51WqNZmLWOx_+6HyrcHMKO_YpNeh=EOsvPznsk-GeQ3fw@mail.gmail.com>

On Wed, Mar 28, 2018 at 04:11:39PM +0100, Emil Velikov wrote:
> On 28 March 2018 at 15:49, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > Quoting Emil Velikov (2018-03-28 02:24:48)
> >> From: Deepak Sharma <deepak.sharma@amd.com>
> >>
> >> Modify vgem_init to take platform dev as parent in drm_dev_init.
> >> This will make drm device available at "/sys/devices/platform/vgem"
> >> in x86 chromebook.
> >>
> >> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> >> Signed-off-by: Deepak Sharma <deepak.sharma@amd.com>
> >> Reviewed-by: Sean Paul <seanpaul@chromium.org>
> >> Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
> >> ---
> >>  drivers/gpu/drm/vgem/vgem_drv.c | 15 +++++++--------
> >>  1 file changed, 7 insertions(+), 8 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
> >> index 2524ff116f00..636ce32fa945 100644
> >> --- a/drivers/gpu/drm/vgem/vgem_drv.c
> >> +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> >> @@ -472,31 +472,30 @@ static int __init vgem_init(void)
> >>         if (!vgem_device)
> >>                 return -ENOMEM;
> >>
> >> -       ret = drm_dev_init(&vgem_device->drm, &vgem_driver, NULL);
> >> -       if (ret)
> >> -               goto out_free;
> >
> > A shame to lose the test coverage this gave us. Care to replace that
> > with a selftest?
> 
> Hi Chris, can you be more specific:
> - What test coverage is lost - some IGT tests/other?
> - Can you provide a rough outline of the test you have in mind?

I think Chris meant the NULL case for drm_dev_init (which was broken
once). But since this series also disallows that with a subsequent patch I
think we're just fine.
-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:[~2018-03-29  7:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28  1:24 [PATCH 1/4] drm/vgem: Fix vgem_init to get drm device avaliable Emil Velikov
2018-03-28  1:24 ` [PATCH 2/4] drm: BUG_ON if passing NULL parent to drm_dev_init Emil Velikov
2018-03-28  7:17   ` Daniel Vetter
2018-03-28  1:24 ` [PATCH 3/4] drm/virtio: remove drm_dev_set_unique workaround Emil Velikov
2018-03-28  7:18   ` Daniel Vetter
2018-03-28 10:27   ` Laszlo Ersek
2018-03-28 14:35     ` Emil Velikov
2018-03-29 11:17       ` Laszlo Ersek
2018-04-03 17:13         ` Emil Velikov
2018-04-04 17:29           ` Laszlo Ersek
2018-04-06 12:15             ` Laszlo Ersek
2018-04-06 12:56               ` Emil Velikov
2018-04-09  8:26                 ` Daniel Vetter
2018-04-09 10:24                   ` Emil Velikov
2018-04-09 11:25                     ` Emil Velikov
2018-04-13 15:45                       ` Daniel Vetter
2018-04-06 13:06               ` Gerd Hoffmann
2018-03-28  1:24 ` [PATCH 4/4] drm: drm_dev_set_unique private, again Emil Velikov
2018-03-28  7:18   ` Daniel Vetter
2018-03-28  7:16 ` [PATCH 1/4] drm/vgem: Fix vgem_init to get drm device avaliable Daniel Vetter
2018-03-28 14:45   ` Emil Velikov
2018-03-28 14:49 ` Chris Wilson
2018-03-28 15:11   ` Emil Velikov
2018-03-29  7:17     ` Daniel Vetter [this message]
2018-04-04 10:46       ` Emil Velikov
2018-04-04 12:07         ` Daniel Vetter

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=20180329071704.GF3881@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.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;
as well as URLs for NNTP newsgroup(s).