From: Christoph Hellwig <hch@infradead.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] tracing/events: introduce __dynamic_array()
Date: Mon, 1 Jun 2009 04:30:04 -0400 [thread overview]
Message-ID: <20090601083004.GB2714@infradead.org> (raw)
In-Reply-To: <4A2384D2.3080403@cn.fujitsu.com>
On Mon, Jun 01, 2009 at 03:35:46PM +0800, Li Zefan wrote:
> __string() is limited:
>
> - it's a char array, but we may want to define array with other types
> - a source string should be available, but we may just know the string size
>
> We introduce __dynamic_array() to break those limitations, and __string()
> becomes a wrapper of it. As a side effect, now __get_str() can be used
> in TP_fast_assign but not only TP_print.
>
> Take XFS for example, we have the string length in the dirent, but the
> string itself is not NULL-terminated, so __dynamic_array() can be used:
Nice one from the users POV! Thanks a lot.
next prev parent reply other threads:[~2009-06-01 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 7:35 [PATCH 1/2] tracing/events: put TP_fast_assign into braces Li Zefan
2009-06-01 7:35 ` [PATCH 2/2] tracing/events: introduce __dynamic_array() Li Zefan
2009-06-01 8:30 ` Christoph Hellwig [this message]
2009-06-01 13:12 ` Steven Rostedt
2009-06-01 16:36 ` Frederic Weisbecker
2009-06-04 12:04 ` [tip:tracing/core] " tip-bot for Li Zefan
2009-06-01 8:29 ` [PATCH 1/2] tracing/events: put TP_fast_assign into braces Christoph Hellwig
2009-06-01 13:11 ` Steven Rostedt
2009-06-01 13:16 ` Frederic Weisbecker
2009-06-04 12:04 ` [tip:tracing/core] " tip-bot for 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=20090601083004.GB2714@infradead.org \
--to=hch@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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
all inboxes | Powered by JetHome®