From: Yiwei Zhang <zzyiwei@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
mingo@redhat.com, elder@kernel.org, federico.vaga@cern.ch,
tony.luck@intel.com, vilhelm.gray@gmail.com,
Linus Walleij <linus.walleij@linaro.org>,
tglx@linutronix.de, yamada.masahiro@socionext.com,
paul.walmsley@sifive.com, Bjorn Helgaas <bhelgaas@google.com>,
Dariusz Marcinkiewicz <darekm@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Joel Fernandes <joelaf@google.com>,
linux-kernel@vger.kernel.org,
Prahlad Kilambi <prahladk@google.com>,
android-kernel <android-kernel@google.com>
Subject: Re: [PATCH v4] gpu/trace: add a gpu total memory usage tracepoint
Date: Mon, 16 Mar 2020 12:28:10 -0700 [thread overview]
Message-ID: <CAKT=dD=g1aK6At4hCyjDNc_S1hR8TUngR7Sm13kgP+tNr4WOmA@mail.gmail.com> (raw)
In-Reply-To: <20200316140544.42e3f383@gandalf.local.home>
On Mon, Mar 16, 2020 at 11:05 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 13 Mar 2020 15:59:37 -0700
> Yiwei Zhang <zzyiwei@google.com> wrote:
>
> > Hi guys, thanks for all the help throughout this. After struggling a
> > while, I failed to figure out when the next merge window is. Could you
> > help point me to the release calendar or something? Thanks again!
>
> I have this queued in my local tree. I'm currently having some issues with
> my testing (there appears to be an unrelated bug to my code keeping it from
> passing). But you should see this patch fly by when I add it to my
> linux-next queue.
>
> -- Steve
Got it. Awesome, thanks Steve!
prev parent reply other threads:[~2020-03-16 19:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 0:32 [PATCH v2] Add gpu memory tracepoints zzyiwei
2020-02-13 0:39 ` Yiwei Zhang
2020-02-13 0:40 ` Greg KH
2020-02-13 1:23 ` Yiwei Zhang
2020-02-13 1:48 ` Steven Rostedt
2020-02-13 2:20 ` zzyiwei
2020-02-13 2:24 ` Yiwei Zhang
2020-02-13 3:29 ` Steven Rostedt
2020-02-13 4:23 ` [PATCH v3] gpu/trace: add " zzyiwei
2020-02-13 4:27 ` Yiwei Zhang
2020-02-13 14:03 ` Steven Rostedt
2020-02-13 17:49 ` Yiwei Zhang
2020-02-24 6:31 ` Yiwei Zhang
2020-02-24 16:38 ` Steven Rostedt
2020-03-01 0:53 ` Yiwei Zhang
2020-03-02 23:48 ` [PATCH] [PATCH v4] gpu/trace: add a gpu total memory usage tracepoint zzyiwei
2020-03-02 23:56 ` Yiwei Zhang
2020-03-02 23:50 ` zzyiwei
2020-03-03 14:07 ` Steven Rostedt
2020-03-03 14:15 ` Greg KH
2020-03-03 14:31 ` Steven Rostedt
2020-03-03 15:15 ` Yiwei Zhang
2020-03-03 15:48 ` Steven Rostedt
2020-03-03 15:56 ` Greg KH
2020-03-13 22:59 ` Yiwei Zhang
2020-03-16 18:05 ` Steven Rostedt
2020-03-16 19:28 ` Yiwei Zhang [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='CAKT=dD=g1aK6At4hCyjDNc_S1hR8TUngR7Sm13kgP+tNr4WOmA@mail.gmail.com' \
--to=zzyiwei@google.com \
--cc=android-kernel@google.com \
--cc=bhelgaas@google.com \
--cc=darekm@google.com \
--cc=elder@kernel.org \
--cc=federico.vaga@cern.ch \
--cc=gregkh@linuxfoundation.org \
--cc=joelaf@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=paul.walmsley@sifive.com \
--cc=prahladk@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vilhelm.gray@gmail.com \
--cc=yamada.masahiro@socionext.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).