[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200224113805.134f8b95@gandalf.local.home>
Date: Mon, 24 Feb 2020 11:38:05 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Yiwei Zhang <zzyiwei@...gle.com>
Cc: mingo@...hat.com, Greg KH <gregkh@...uxfoundation.org>,
elder@...nel.org, federico.vaga@...n.ch, tony.luck@...el.com,
vilhelm.gray@...il.com, Linus Walleij <linus.walleij@...aro.org>,
tglx@...utronix.de, yamada.masahiro@...ionext.com,
paul.walmsley@...ive.com, linux-kernel@...r.kernel.org,
Prahlad Kilambi <prahladk@...gle.com>,
Joel Fernandes <joelaf@...gle.com>,
android-kernel <android-kernel@...gle.com>
Subject: Re: [PATCH v3] gpu/trace: add gpu memory tracepoints
On Sun, 23 Feb 2020 22:31:11 -0800
Yiwei Zhang <zzyiwei@...gle.com> wrote:
> Dear gpu and tracing owners,
>
> It's been a while and this is just a gentle and friendly re-ping for
> review of this small patch.
I guess the question is what tree should this go through. I usually
only take tracing infrastructure changes and leave topic specific
tracing for those that maintain the topics.
I'm fine with taking this through my tree if I get a bunch of
acked/reviewed by from other maintainers.
-- Steve
Powered by blists - more mailing lists