From: Pavel Machek <pavel@ucw.cz>
To: Robert Love <rml@tech9.net>
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: Tue, 22 Oct 2002 01:08:57 +0200 [thread overview]
Message-ID: <20021021230856.GA120@elf.ucw.cz> (raw)
In-Reply-To: <1034885077.718.595.camel@phantasy>
Hi!
> > Can't you just left the old, nuerical one in even if CONFIG_KALLSYMS
> > ise set? One ifdef less and far less surprises..
>
> But why? Save the call to get_wchan()...
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.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-10-26 10:24 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 [this message]
2002-10-26 17:44 ` Robert Love
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=20021021230856.GA120@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rml@tech9.net \
--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 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.