From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Jeff Garzik <jgarzik@pobox.com>, Yum Rayan <yum.rayan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Reduce stack usage in time.c
Date: Thu, 31 Mar 2005 15:00:17 +0200 [thread overview]
Message-ID: <20050331130017.GA19294@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200503311226.58037.vda@ilport.com.ua>
On Thu, 31 March 2005 12:26:58 +0300, Denis Vlasenko wrote:
>
> Is this a syscall?
> Is it ever called from some deeply nested kernel function?
Never showed up in any of my callchain-tests. I'd leave it as is.
Jörn
--
When I am working on a problem I never think about beauty. I think
only how to solve the problem. But when I have finished, if the
solution is not beautiful, I know it is wrong.
-- R. Buckminster Fuller
prev parent reply other threads:[~2005-03-31 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 7:46 Yum Rayan
2005-03-31 8:26 ` Jeff Garzik
2005-03-31 9:26 ` Denis Vlasenko
2005-03-31 13:00 ` Jörn Engel [this message]
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=20050331130017.GA19294@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
--cc=yum.rayan@gmail.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
all inboxes | Powered by JetHome®