From: Linus Walleij <linus.walleij@linaro.org>
To: Eric Anholt <eric@anholt.net>
Cc: Russell King <linux@armlinux.org.uk>,
DRI Development <dri-devel@lists.freedesktop.org>,
Sean Paul <sean@poorly.run>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/4] drm: pl111: Update documentation
Date: Tue, 9 Jun 2020 22:17:46 +0200 [thread overview]
Message-ID: <CACRpkdbY=ALou98n6uW8C5Wwup1-qyaNZhqTSwC8B5FydjbgQA@mail.gmail.com> (raw)
In-Reply-To: <CADaigPX_9mBqr3hKA0-aC-TOY3hEnXnQremMiPopw8DUcGCzgQ@mail.gmail.com>
On Tue, Jun 9, 2020 at 10:11 PM Eric Anholt <eric@anholt.net> wrote:
> FWIW, series is Reviewed-by: Eric Anholt <eric@anholt.net>
Thanks Eric, do I remember correct that you were using this
driver for something like a clock display? Are you still using it
for that?
Nowadays the biggest user is arguably the ARM FVP emulator
which is running a full Android stack using this driver.
Yours,
Linus Walleij
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-06-09 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 20:04 [PATCH 1/4] drm: pl111: Credit where credit is due Linus Walleij
2020-06-09 20:04 ` [PATCH 2/4] video: fbdev: amba-clcd: Retire elder CLCD driver Linus Walleij
2020-09-15 1:10 ` Peter Collingbourne
2020-09-21 21:32 ` Linus Walleij
2020-09-22 4:10 ` Peter Collingbourne
2020-09-22 19:43 ` Peter Collingbourne
2020-06-09 20:04 ` [PATCH 3/4] drm: pl111: Absorb the external register header Linus Walleij
2020-06-09 20:04 ` [PATCH 4/4] drm: pl111: Update documentation Linus Walleij
2020-06-09 20:10 ` Eric Anholt
2020-06-09 20:17 ` Linus Walleij [this message]
2020-06-09 20:53 ` Eric Anholt
2020-06-10 7:37 ` kernel test robot
2020-06-12 11:04 ` Linus Walleij
2020-06-12 11:14 ` Sam Ravnborg
2020-06-12 12:40 ` [kbuild-all] " Philip Li
2020-06-22 9:28 ` Rong Chen
2020-06-16 16:12 ` Emil Velikov
2020-06-17 0:33 ` Philip Li
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='CACRpkdbY=ALou98n6uW8C5Wwup1-qyaNZhqTSwC8B5FydjbgQA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=sean@poorly.run \
/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).