From: Sam Ravnborg <sam@ravnborg.org>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
hdegoede@redhat.com
Subject: Re: [PATCH 0/3] drm/tinydrm: Rename to drm/tiny
Date: Thu, 25 Jul 2019 17:10:47 +0200 [thread overview]
Message-ID: <20190725151047.GA12176@ravnborg.org> (raw)
In-Reply-To: <9783d219-d044-83a9-66d2-f7f36713f9eb@tronnes.org>
Hi Noralf.
On Thu, Jul 25, 2019 at 02:46:08PM +0200, Noralf Trønnes wrote:
>
>
> Den 25.07.2019 14.06, skrev Daniel Vetter:
> > On Thu, Jul 25, 2019 at 12:51:29PM +0200, Noralf Trønnes wrote:
> >> This is the final polish on tinydrm turning it into _the_ place for tiny
> >> DRM drivers.
> >>
> >> Noralf.
> >>
> >> Noralf Trønnes (3):
> >> drm/tinydrm/Kconfig: Remove menuconfig DRM_TINYDRM
> >> drm/tinydrm: Rename folder to tiny
> >> drm/gm12u320: Move driver to drm/tiny
I have thrown the patch-set after my usual build testing.
Looks good - so you can consider the full series:
Acked-by: Sam Ravnborg <sam@ravnborg.org>
> >
> > I wonder whether we could place a documentation hint somewhere to put
> > tiny drm drivers (i.e. one file only, and that one pretty small) into
> > drm/tiny. But I couldn't come up with a good place. Maybe re-add tiny.rst
> > with a short overview paragraph that points at the most useful helpers for
> > tiny drivers, plus how to integrate them? Kinda as a FAQ to the "I want to
> > port an fbdev driver, halp pls?" question.
> >
>
> Sam, is this something you could do, you giving a talk about this and
> everything :-)
Talk proposal is accepted, but I need to get a few details in order
here. (work, family stuff).
And then I also hope to actaully create a first tiny driver - awaiting
display to arrive by mail.
But if that all succeeds then I will be happy to try to come up with
something that would have helped me.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-25 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 10:51 [PATCH 0/3] drm/tinydrm: Rename to drm/tiny Noralf Trønnes
2019-07-25 10:51 ` [PATCH 1/3] drm/tinydrm/Kconfig: Remove menuconfig DRM_TINYDRM Noralf Trønnes
2019-07-30 13:19 ` Hans de Goede
2019-07-30 13:34 ` Noralf Trønnes
2019-07-30 13:35 ` Hans de Goede
2019-07-30 13:53 ` Emil Velikov
2019-07-30 14:03 ` Noralf Trønnes
2019-07-30 14:16 ` Emil Velikov
2019-10-01 12:36 ` [1/3] " Jason Gunthorpe
2019-10-01 13:28 ` Noralf Trønnes
2019-10-01 13:45 ` Jason Gunthorpe
2019-10-01 14:07 ` Noralf Trønnes
2019-10-09 10:45 ` Daniel Vetter
2019-10-09 12:48 ` Noralf Trønnes
2019-10-09 13:31 ` Maxime Ripard
2019-10-10 13:30 ` Noralf Trønnes
2019-07-25 10:51 ` [PATCH 2/3] drm/tinydrm: Rename folder to tiny Noralf Trønnes
2019-07-25 10:51 ` [PATCH 3/3] drm/gm12u320: Move driver to drm/tiny Noralf Trønnes
2019-07-25 12:06 ` [PATCH 0/3] drm/tinydrm: Rename " Daniel Vetter
2019-07-25 12:46 ` Noralf Trønnes
2019-07-25 15:10 ` Sam Ravnborg [this message]
2019-07-31 13:32 ` Noralf Trønnes
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=20190725151047.GA12176@ravnborg.org \
--to=sam@ravnborg.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=noralf@tronnes.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