From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>, Peiyong Lin <lpy@google.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sidath Senanayake <sidaths@google.com>,
linux-kernel@vger.kernel.org,
Amit Kucheria <amit.kucheria@linaro.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Prahlad Kilambi <prahladk@google.com>,
Ingo Molnar <mingo@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Pavel Machek <pavel@ucw.cz>,
Paul Walmsley <paul.walmsley@sifive.com>,
zzyiwei@android.com, android-kernel@google.com
Subject: Re: [PATCH v4] Add power/gpu_frequency tracepoint.
Date: Tue, 17 Nov 2020 19:00:35 +0100 [thread overview]
Message-ID: <173158b7-e65e-257f-0e24-aa9d5401d1d1@intel.com> (raw)
In-Reply-To: <20201116160508.3e86496f@gandalf.local.home>
On 11/16/2020 10:05 PM, Steven Rostedt wrote:
> On Mon, 16 Nov 2020 12:55:29 -0800
> Peiyong Lin <lpy@google.com> wrote:
>
>> Hi there,
>>
>> May I ask whether the merge window has passed? If so is it possible to
>> ask for a review?
> This is up to the maintainers of power management to accept this.
>
> Rafael?
I'd say up to the GPU people rather (dri-devel CCed) since that's where
it is going to be used.
Also it would be good to see at least one in-the-tree user of this (or a
usage example at least).
Cheers!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2020-11-17 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200820162738.33053904@oasis.local.home>
[not found] ` <20201022173434.910879-1-lpy@google.com>
[not found] ` <CA+0soAkD7BG6CjhMW6PYR4yAgDykU2uUizcHx1QQdXqgesCFFg@mail.gmail.com>
[not found] ` <20201116160508.3e86496f@gandalf.local.home>
2020-11-17 18:00 ` Rafael J. Wysocki [this message]
2020-11-17 18:10 ` [PATCH v4] Add power/gpu_frequency tracepoint Alex Deucher
2020-11-17 21:31 ` Peiyong Lin
2020-11-30 22:33 ` Peiyong Lin
2020-12-02 12:34 ` Brian Starkey
2020-12-21 20:10 ` [PATCH v5] " Peiyong Lin
2021-03-10 21:56 ` Peiyong Lin
2021-03-12 18:08 ` Pavel Machek
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=173158b7-e65e-257f-0e24-aa9d5401d1d1@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=amit.kucheria@linaro.org \
--cc=android-kernel@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpy@google.com \
--cc=mingo@redhat.com \
--cc=paul.walmsley@sifive.com \
--cc=pavel@ucw.cz \
--cc=prahladk@google.com \
--cc=rostedt@goodmis.org \
--cc=sidaths@google.com \
--cc=ulf.hansson@linaro.org \
--cc=yamada.masahiro@socionext.com \
--cc=zzyiwei@android.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