From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Paul Fulghum <paulkf@microgate.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [PATCH] Use tty_schedule in VT code.
Date: Tue, 17 Jul 2007 13:42:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707171340360.27353@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707172050180.9131@pentafluge.infradead.org>
On Tue, 17 Jul 2007, James Simmons wrote:
>
> Because sometimes you do want the delay. In other parts of the tty
> code we do delay.
Ahh, ok, in that it's ok by me.
> What should be done is
>
> if (tty->low_latency)
> flush_to_ldisc(&tty->buf.work.work);
> else
> schedule_delayed_work(&tty->buf.work, 1);
>
> Is this acceptable to you?
In that case, we might as well just always do the scheduled_delayed_work()
with a zero timeout as per the earlier patch. I'd still like to know who
*cares*, though? Why not leave it at 1?
Linus
next prev parent reply other threads:[~2007-07-17 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 18:37 James Simmons
2007-07-17 18:49 ` Samuel Thibault
2007-07-17 19:17 ` James Simmons
2007-07-17 20:31 ` Paul Fulghum
2007-07-17 19:24 ` Linus Torvalds
2007-07-17 20:35 ` Paul Fulghum
2007-07-17 19:44 ` Linus Torvalds
2007-07-17 19:52 ` James Simmons
2007-07-17 20:42 ` Linus Torvalds [this message]
2007-07-17 23:35 ` Alan Cox
2007-07-18 18:17 ` James Simmons
2007-07-18 18:27 ` Paul Fulghum
2007-07-18 19:57 ` James Simmons
2007-07-18 21:12 ` Paul Fulghum
2007-07-18 20:08 ` Linus Torvalds
2007-07-18 21:36 ` Alan Cox
2007-07-17 21:06 ` Paul Fulghum
2007-07-17 20:15 ` James Simmons
2007-07-17 21:33 ` Paul Fulghum
2007-07-18 17:19 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2007-05-08 20:10 James Simmons
2007-05-08 20:32 ` Paul Fulghum
2007-05-09 20:58 ` Paul Fulghum
2007-05-09 20:56 ` James Simmons
2007-05-09 23:02 ` Paul Fulghum
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=alpine.LFD.0.999.0707171340360.27353@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=paulkf@microgate.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®