From: Daniel Vetter <daniel@ffwll.ch>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: "Marek Vasut" <marex@denx.de>,
"Simon Shields" <simon@lineageos.org>,
lima@lists.freedesktop.org,
"Andreas Baierl" <ichgeh@imkreisrum.de>,
"Maxime Ripard" <maxime.ripard@bootlin.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"David Airlie" <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Vasily Khoruzhick" <anarsoul@gmail.com>,
"Qiang Yu" <yuq825@gmail.com>, "Sam Ravnborg" <sam@ravnborg.org>,
"Sean Paul" <sean@poorly.run>,
"Erico Nunes" <nunes.erico@gmail.com>
Subject: Re: [PATCH v8] drm/lima: driver for ARM Mali4xx GPUs
Date: Thu, 28 Mar 2019 15:25:53 +0100 [thread overview]
Message-ID: <20190328142553.GY2665@phenom.ffwll.local> (raw)
In-Reply-To: <ca4d8a47-9f99-4d15-6ecf-ce142ccee26f@baylibre.com>
On Thu, Mar 28, 2019 at 03:12:23PM +0100, Neil Armstrong wrote:
> On 27/03/2019 20:06, Eric Anholt wrote:
> > Neil Armstrong <narmstrong@baylibre.com> writes:
> >
> >> Hi,
> >>
> >> On 26/03/2019 21:40, Vasily Khoruzhick wrote:
> >>> Hi,
> >>>
> >>> So what's the status of it?
> >>
> >> We are waiting on ARM to give a feedback on the ARM GPU tile modifier,
> >> see https://patchwork.freedesktop.org/patch/292187/?series=57996&rev=1
> >
> > I don't see any dependency of this patch on the modifier definition.
> >
>
> Indeed no direct dependency, so no reason to not apply it.
>
> Daniel, who should merge this then ?
Add Quang as drm-misc maintainer, merge it there? At least a pile of
people participating in that thread are committers already. Either way
needs a MAINTAINERS entry to note where it actually is.
Ideally I guess we'd stuff it into the same place as panfrost later on.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-28 14:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 12:20 [PATCH v8] drm/lima: driver for ARM Mali4xx GPUs Qiang Yu
2019-03-10 1:01 ` kbuild test robot
2019-03-10 2:00 ` kbuild test robot
2019-03-10 2:40 ` Qiang Yu
2019-03-11 15:37 ` Rob Herring
2019-03-12 1:54 ` Qiang Yu
2019-03-12 8:11 ` Heiko Stuebner
2019-03-26 20:40 ` Vasily Khoruzhick
2019-03-27 9:15 ` Neil Armstrong
2019-03-27 13:53 ` Brian Starkey
2019-03-27 14:27 ` Rob Herring
2019-03-27 16:33 ` Eric Anholt
2019-03-27 19:06 ` Eric Anholt
2019-03-28 14:12 ` Neil Armstrong
2019-03-28 14:25 ` Daniel Vetter [this message]
2019-03-28 21:31 ` Eric Anholt
2019-03-29 2:29 ` Qiang Yu
2019-03-29 13:47 ` [PATCH] MAINTAINERS: add drm/lima driver info Qiang Yu
2019-03-29 14:37 ` [Lima] " Neil Armstrong
2019-03-29 15:20 ` Daniel Vetter
2019-03-30 12:31 ` Qiang Yu
2019-04-01 17:48 ` Eric Anholt
2019-04-02 2:30 ` Qiang Yu
2019-04-03 11:53 ` Qiang Yu
2019-04-03 12:46 ` Daniel Vetter
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=20190328142553.GY2665@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=anarsoul@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ichgeh@imkreisrum.de \
--cc=lima@lists.freedesktop.org \
--cc=marex@denx.de \
--cc=maxime.ripard@bootlin.com \
--cc=narmstrong@baylibre.com \
--cc=nunes.erico@gmail.com \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
--cc=simon@lineageos.org \
--cc=yuq825@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox