From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Alyssa Rosenzweig <alyssa@collabora.com>, Rob Herring <robh@kernel.org>
Cc: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Steven Price <steven.price@arm.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/panfrost: Dynamically allocate pm_domains
Date: Wed, 16 Feb 2022 10:01:15 +0100 [thread overview]
Message-ID: <2cb4a1b6-1028-a1df-b7ff-9be7a57dd141@collabora.com> (raw)
In-Reply-To: <Ygwp+LDliCnbkMZQ@maud>
Il 15/02/22 23:32, Alyssa Rosenzweig ha scritto:
>> I'd do the oneliner changing it to 5 and be done with it. That being
>> said, we have plenty of examples of doing this both ways, so whatever
>> makes people happy.
>
> Excellent, that's the patch I wrote originally :-)
>
> Dropping this patch, unless Angelo (or someone else) strongly objects.
Concretely measuring would be great, but I have no strong objections about
perhaps delaying this research to another (near or far) moment.
Let's drop this for now.
prev parent reply other threads:[~2022-02-16 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 20:31 [PATCH] drm/panfrost: Dynamically allocate pm_domains Alyssa Rosenzweig
2022-02-14 20:55 ` Alyssa Rosenzweig
2022-02-15 9:23 ` AngeloGioacchino Del Regno
2022-02-15 12:09 ` Robin Murphy
2022-02-15 21:53 ` Rob Herring
2022-02-15 22:32 ` Alyssa Rosenzweig
2022-02-16 9:01 ` AngeloGioacchino Del Regno [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=2cb4a1b6-1028-a1df-b7ff-9be7a57dd141@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=alyssa@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=steven.price@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).