From: Robert Love <rml@tech9.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
riel@conectiva.com.br
Subject: Re: [PATCH] pre-decoded wchan output
Date: 26 Oct 2002 13:44:40 -0400 [thread overview]
Message-ID: <1035654281.1501.7596.camel@phantasy> (raw)
In-Reply-To: <20021021230856.GA120@elf.ucw.cz>
On Mon, 2002-10-21 at 19:08, Pavel Machek wrote:
> Yes, and force users to update procps for no good reason. And "new"
> procps will still need code to deal with get_wchan themselves... Plus
> you loose information by killing get_wchan() -- two different wait
> points in one function seems very possible to me.
- users of 2.5 need a new procps but only wchan is "broken" and
only if CONFIG_KALLSYMS is set anyhow
- I did not kill get_wchan, just do not use it in stat - in fact
I use it in the new wchan approach, too
- its not an issue now because the updated patch (posted 5 days
after this email you are replying to) keeps wchan.
So you got your way. Look at the patch posted 22 Oct. It is now in
2.5-mm.
Robert Love
next prev parent reply other threads:[~2002-10-26 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 19:14 [PATCH] pre-decoded wchan output Robert Love
2002-10-17 19:58 ` Christoph Hellwig
2002-10-17 20:04 ` Robert Love
2002-10-21 23:08 ` Pavel Machek
2002-10-26 17:44 ` Robert Love [this message]
2002-10-20 22:04 ` David =?ISO-8859-1?Q?G=F3mez=22?= <david@pleyades.net>
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=1035654281.1501.7596.camel@phantasy \
--to=rml@tech9.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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