All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: rostedt@goodmis.org, Li Zefan <lizf@cn.fujitsu.com>
Cc: airlied@linux.ie, chris@chris-wilson.co.uk,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] drm/i915: Convert more trace events to DEFINE_EVENT
Date: Wed, 26 May 2010 12:00:55 -0700	[thread overview]
Message-ID: <87bpc2lc7s.fsf@pollan.anholt.net> (raw)
In-Reply-To: <1274818126.22648.221.camel@gandalf.stny.rr.com>

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

On Tue, 25 May 2010 16:08:46 -0400, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 2010-05-24 at 16:25 +0800, Li Zefan wrote:
> > Convert i915_gem_object_clflush to DEFINE_EVENT, and save ~0.5K:
> > 
> >    text    data     bss     dec     hex filename
> >   13204    2732      12   15948    3e4c i915_trace_points.o.orig
> >   12668    2732      12   15412    3c34 i915_trace_points.o
> > 
> > No change in functionality.
> > 
> 
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> 
> I'm expecting that this will be going through the DRM/i915 path.

Yeah.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2010-05-26 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24  8:25 [PATCH] drm/i915: Convert more trace events to DEFINE_EVENT Li Zefan
2010-05-25  3:36 ` Steven Rostedt
2010-05-25  3:36 ` Steven Rostedt
2010-05-25 20:08 ` Steven Rostedt
2010-05-25 20:08 ` Steven Rostedt
2010-05-26 19:00   ` Eric Anholt
2010-05-26 19:00   ` Eric Anholt [this message]
2010-05-26 20:49 ` Eric Anholt
2010-05-26 20:49 ` Eric Anholt
  -- strict thread matches above, loose matches on Subject: below --
2010-05-24  8:25 Li Zefan

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=87bpc2lc7s.fsf@pollan.anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.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.