From: Fabian Vogt <fabian@ritter-vogt.de>
To: linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Cc: Daniel Tang <dt.tangr@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: PL111 DRM for TI Nspire
Date: Tue, 28 May 2019 18:49:58 +0200 [thread overview]
Message-ID: <15933797.6b6mW1LQZ0@linux-e202.suse.de> (raw)
In-Reply-To: <F4EF7060-DEC5-4122-8D51-B5DC3F1D553E@gmail.com>
Hi,
Just subscribed to this ML to be able to answer here properly.
Am Dienstag, 21. Mai 2019, 17:24:19 CEST schrieb Daniel Tang:
> Hi Linus,
>
> Thanks for reaching out. At this stage, I?m not able to personally test patches as I?m no longer actively developing on this platform. However, I will reach out and direct your request to some people who can help (and hopefully find a more appropriate maintainer).
>
> I will try to get back to you as soon as possible.
>
> Cheers,
> Daniel
>
> > On 21 May 2019, at 10:52 am, Linus Walleij <linus.walleij at linaro.org> wrote:
> >
> > Hi folks,
> >
> > I have one more user of the old PL111 fbdev driver before I can
> > switch them all over to the new DRM driver in drivers/gpu/drm/pl111
> > and finally delete the old driver: TI Nspire.
> >
> > Before I invest time I want to ascertain that the maintainers are
> > actively using Nspire and can test patches in reasonable time if
> > I work on this, since I cannot test it myself.
> >
> > It seems easy enough to convert that I would dare dry-coding it
> > if I can get some help testing and fixing up rough edges.
> >
> > Is Nspire ready to test some patches?
Yes! Just point me to whatever tree to test with which patches on top and I'll
give them a test run or two.
Cheers,
Fabian
> > Yours,
> > Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-28 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 1:52 PL111 DRM for TI Nspire Linus Walleij
2019-05-21 15:24 ` Daniel Tang
2019-05-28 16:49 ` Fabian Vogt [this message]
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=15933797.6b6mW1LQZ0@linux-e202.suse.de \
--to=fabian@ritter-vogt.de \
--cc=dt.tangr@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.