From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Gustavo Padovan <gustavo@padovan.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dma-buf/fence: fix timeline str value on fence_annotate_wait_on
Date: Thu, 21 Jan 2016 18:09:05 -0200 [thread overview]
Message-ID: <20160121200905.GB2507@joana> (raw)
In-Reply-To: <20160121195802.GA18488@kroah.com>
2016-01-21 Greg KH <gregkh@linuxfoundation.org>:
> On Thu, Jan 21, 2016 at 09:48:14AM -0200, Gustavo Padovan wrote:
> > From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >
> > timeline was wrongly assigned with ->get_driver_name().
> >
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > ---
> > include/trace/events/fence.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/trace/events/fence.h b/include/trace/events/fence.h
> > index 98feb1b..d6dfa05 100644
> > --- a/include/trace/events/fence.h
> > +++ b/include/trace/events/fence.h
> > @@ -17,7 +17,7 @@ TRACE_EVENT(fence_annotate_wait_on,
> >
> > TP_STRUCT__entry(
> > __string(driver, fence->ops->get_driver_name(fence))
> > - __string(timeline, fence->ops->get_driver_name(fence))
> > + __string(timeline, fence->ops->get_timeline_name(fence))
> > __field(unsigned int, context)
> > __field(unsigned int, seqno)
>
> Why would you send this to: me? I am not the trace maintainer...
Because you are the original committer of the file. But this should have
been addressed to the trace maintainer.
Gustavo
next prev parent reply other threads:[~2016-01-21 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 11:48 [PATCH] dma-buf/fence: fix timeline str value on fence_annotate_wait_on Gustavo Padovan
2016-01-21 19:58 ` Greg KH
2016-01-21 20:09 ` Gustavo Padovan [this message]
2016-01-21 20:34 ` Greg KH
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=20160121200905.GB2507@joana \
--to=gustavo.padovan@collabora.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.