From: "Frank Wunderlich" <frank-w@public-files.de>
To: "Matthias Brugger" <matthias.bgg@gmail.com>
Cc: "CK Hu" <ck.hu@mediatek.com>, "Daniel Vetter" <daniel@ffwll.ch>,
srv_heupstream@mediatek.com, "David Airlie" <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"\"Noralf Tr�nnes\"" <noralf@tronnes.org>,
linux-mediatek@lists.infradead.org,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Aw: Re: [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device
Date: Fri, 18 Jan 2019 13:33:59 +0100 [thread overview]
Message-ID: <trinity-059802f2-322f-46a5-9031-02582b115000-1547814839147@3c-app-gmx-bs12> (raw)
In-Reply-To: <74eba84d-4686-698a-6100-d72dabd15a21@gmail.com>
I have tested same codebase where my FBDev-Patch works (4.20-hdmiv5), only without it and CK Hu's 2 Patches
does generic fbdev depend on the mmsys-Patch?
regards Frank
> Gesendet: Freitag, 18. Januar 2019 um 09:39 Uhr
> Von: "Matthias Brugger" <matthias.bgg@gmail.com>
> may it be the not yet fixed mmsys compatible problem?
> Frank, did you test with my last series [1]?
>
> Regards,
> Matthias
>
> [1] https://patchwork.kernel.org/cover/10686345/
next prev parent reply other threads:[~2019-01-18 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 1:39 [PATCH 1/2] drm/mediatek: Implement gem prime vmap/vunmap function CK Hu
2019-01-16 1:39 ` [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device CK Hu
2019-01-17 14:14 ` Aw: " Frank Wunderlich
2019-01-18 1:46 ` CK Hu
2019-01-18 8:39 ` Matthias Brugger
2019-01-18 12:33 ` Frank Wunderlich [this message]
2019-01-20 13:36 ` Aw: " Frank Wunderlich
2019-03-19 3:12 ` CK Hu
2019-03-19 16:52 ` Aw: " Frank Wunderlich
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=trinity-059802f2-322f-46a5-9031-02582b115000-1547814839147@3c-app-gmx-bs12 \
--to=frank-w@public-files.de \
--cc=airlied@linux.ie \
--cc=ck.hu@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=noralf@tronnes.org \
--cc=p.zabel@pengutronix.de \
--cc=srv_heupstream@mediatek.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).