From: Christoph Hellwig <hch@infradead.org>
To: Josh Stone <jistone@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jason Baron <jbaron@redhat.com>,
mingo@elte.hu, rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] export softirq_to_name symbol
Date: Fri, 1 May 2009 16:22:46 -0400 [thread overview]
Message-ID: <20090501202246.GA20056@infradead.org> (raw)
In-Reply-To: <49FB58F7.8080109@redhat.com>
On Fri, May 01, 2009 at 01:17:59PM -0700, Josh Stone wrote:
> More precisely, it's the piece of code that copies the trace into an
> __entry pointer. In my case, __entry has nothing to do with the ring
> buffer.
Well, it should be the ring buffer. If you want to do something more
fancy rewrite it in proper C code and submit a patch for discussion to
lkml.
next prev parent reply other threads:[~2009-05-01 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 19:30 [PATCH] export softirq_to_name symbol Jason Baron
2009-05-01 19:50 ` Christoph Hellwig
2009-05-01 20:07 ` Josh Stone
2009-05-01 20:10 ` Christoph Hellwig
2009-05-01 20:17 ` Josh Stone
2009-05-01 20:22 ` Christoph Hellwig [this message]
2009-05-01 21:25 ` Josh Stone
2009-05-03 18:36 ` Frederic Weisbecker
2009-05-03 8:33 ` Ingo Molnar
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=20090501202246.GA20056@infradead.org \
--to=hch@infradead.org \
--cc=jbaron@redhat.com \
--cc=jistone@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox