From: Liming Wang <liming.wang@windriver.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] function tracing: fix wrong position computing of stack_trace
Date: Fri, 21 Nov 2008 11:00:17 +0800 [thread overview]
Message-ID: <1227236418-6023-1-git-send-email-liming.wang@windriver.com> (raw)
Hi Steven and Ingo,
Before I have submitted a patch to fix output of available_filter_functions,
later I checked other places that use seq_operations, I found stack_trace
also has this potential problem.
This fix use a more sane method to implement seq_operations. And this avoids
checking return value of seq_printf. If you think this implementation is OK,
I think others can be convert to this cleaner way, which will make future
usage of seq_operations less errors.
walimis
next reply other threads:[~2008-11-21 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 3:00 Liming Wang [this message]
2008-11-21 3:00 ` [PATCH 1/1] " Liming Wang
2008-11-21 7:52 ` Ingo Molnar
2008-11-21 8:13 ` Wang Liming
2008-11-21 13:14 ` Steven Rostedt
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=1227236418-6023-1-git-send-email-liming.wang@windriver.com \
--to=liming.wang@windriver.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
all inboxes | Powered by JetHome®