From: Paul Fulghum <paulkf@microgate.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Char: tty, add tty_schedule_wakeup
Date: Thu, 01 Nov 2007 08:34:27 -0600 [thread overview]
Message-ID: <4729E3F3.2090602@microgate.com> (raw)
In-Reply-To: <15530290543226725036.slaby@karneval.cz>
Jiri Slaby wrote:
> + * Functionally the same as tty_wakeup, but it can be used in hot
> + * paths. since the wakeup is scheduled and done in the future.
>
I'm not familiar with the terminology 'hot paths',
what do you mean by that?
Do you have an example of where you intend to
use this new facility? The patch does not include
such an example so it is difficult for me to see
why you are adding this function.
--
Paul Fulghum
Microgate Systems, Ltd
next prev parent reply other threads:[~2007-11-01 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 10:55 [RFC 1/2] Char: tty, centralize works Jiri Slaby
2007-11-01 10:55 ` [PATCH 2/2] Char: tty, add tty_schedule_wakeup Jiri Slaby
2007-11-01 14:34 ` Paul Fulghum [this message]
2007-11-01 15:07 ` Jiri Slaby
2007-11-01 15:48 ` Alan Cox
2007-11-01 15:50 ` Jiri Slaby
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=4729E3F3.2090602@microgate.com \
--to=paulkf@microgate.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.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