From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: nd <nd@arm.com>, "kernel@collabora.com" <kernel@collabora.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
David Airlie <airlied@linux.ie>,
Ezequiel Garcia <ezequiel@collabora.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
Maxime Ripard <mripard@kernel.org>,
Ayan Halder <Ayan.Halder@arm.com>, Sean Paul <sean@poorly.run>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] drm/rockchip: Add AFBC support
Date: Wed, 25 Sep 2019 11:42:16 +0200 [thread overview]
Message-ID: <e5fdc7ff-6171-6190-1bca-9f517f69b03c@collabora.com> (raw)
In-Reply-To: <20190925093913.z4vduybwcokn3awi@DESKTOP-E1NTVVP.localdomain>
Hi Brian,
W dniu 25.09.2019 o 11:39, Brian Starkey pisze:
> Hi Andrzej,
>
> Thanks for the patch, it's nice to see another AFBC implementation
> coming in.
>
I did a false start, though. But the work is in progress. Thanks for the review,
anyway.
> For future versions, could you please Cc ayan.halder@arm.com? It would
> have been nice to have someone @arm.com on patches which use/impact
> Arm modifiers. Sadly I don't know how to make get_maintainer.pl help
Of course.
Andrzej
_______________________________________________
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-09-25 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 12:20 [PATCH] drm/rockchip: Add AFBC support Andrzej Pietrasiewicz
2019-09-23 13:53 ` Neil Armstrong
2019-09-23 15:34 ` Andrzej Pietrasiewicz
2019-09-25 9:28 ` Ayan Halder
2019-09-25 9:35 ` Ayan Halder
2019-09-25 11:12 ` Daniel Vetter
2019-09-25 9:39 ` Brian Starkey
2019-09-25 9:42 ` Andrzej Pietrasiewicz [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=e5fdc7ff-6171-6190-1bca-9f517f69b03c@collabora.com \
--to=andrzej.p@collabora.com \
--cc=Ayan.Halder@arm.com \
--cc=Brian.Starkey@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=sean@poorly.run \
--cc=tomeu.vizoso@collabora.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