From: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: CK Hu <ck.hu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
MOHAMMAD RASIM
<mohammad.rasim96-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Fabien Parent <fparent-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Cc: linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: Wiki to track changes and progress ?
Date: Mon, 2 Sep 2019 13:17:33 +0200 [thread overview]
Message-ID: <de61f89b-ad6d-e8e0-04b2-70ae2ebb29e6@gmail.com> (raw)
In-Reply-To: <1567129347.30548.4.camel@mtksdaap41>
+Fabien
On 30/08/2019 03:42, CK Hu wrote:
> Hi, Matthias:
>
> On Thu, 2019-08-29 at 12:41 +0200, Matthias Brugger wrote:
>> Hi Mohammad,
>>
>> On 25/09/2018 21:36, MOHAMMAD RASIM wrote:
>>> Hi,
>>>
>>> Is there a wiki for linux-mediatek where I can see the progress of mainlining,
>>> what works and what doesn't (status matrix) ?
>>>
>>> Something similar to other projects like http://linux-meson.com/doku.php and
>>> http://linux-sunxi.org/Linux_mainlining_effort
>>>
>>
>> I recently updated the table. It is not complete but at least to some extent
>> useful. Especially mt8173 and mt8183 need an update.
>>
>> https://mtk.bcnfs.org/doku.php?id=linux_mainline_effort
>>
>
> In that table, MT8167 DRM is WIP (work in progress), I've no idea about
> this, could you provide the information about MT8167 DRM? I'm sure that
> MT8183 DRM is WIP.
I tried to find it out by going through the history of the table. But TBH it is
difficult to read...
I think Fabien is working on MT8167, so I suppose he added the WIP.
Regards,
Matthias
prev parent reply other threads:[~2019-09-02 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:36 Wiki to track changes and progress ? MOHAMMAD RASIM
[not found] ` <256e20ee-ce22-2ff8-a2c7-cde75fc681e2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-09-26 8:35 ` Matthias Brugger
2019-08-29 10:41 ` Matthias Brugger
[not found] ` <e242d481-6a08-4076-2aaf-44b3c4a6afdb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-08-30 1:42 ` CK Hu
2019-09-02 11:17 ` Matthias Brugger [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=de61f89b-ad6d-e8e0-04b2-70ae2ebb29e6@gmail.com \
--to=matthias.bgg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ck.hu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=fparent-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mohammad.rasim96-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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