From: Joe Peterson <joe@skyrush.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] n-tty-output-bells-immediately
Date: Sat, 25 Oct 2008 09:53:01 -0600 [thread overview]
Message-ID: <490340DD.9010605@skyrush.com> (raw)
In-Reply-To: <20081025164829.0b602e6e@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> BTW, where are the patches sitting at this point? I saw an email about
>> "linux-next" that lists just the first of the 3 (the drop bkl one); and
>> your tty git is now empty. Just curious.
>
> Stephen asked that there was nothing being picked up for next that wasn't
> .28 material for the moment.
Oh, ok, so the echo/bkl-drop one is in .28, and the other 2 in .29?
Sounds good. Do you just queue them yourself, or are they in some other
git now?
-Joe
next prev parent reply other threads:[~2008-10-25 15:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 6:01 [PATCH] fix n_tty/pty input/output buffer full and other misc char handling Joe Peterson
2008-10-13 8:40 ` Alan Cox
2008-10-22 9:32 ` Alan Cox
2008-10-22 19:35 ` Joe Peterson
2008-10-23 1:33 ` Joe Peterson
2008-10-23 1:34 ` [PATCH] n-tty-fix-cont-and-ctrl-output Joe Peterson
2008-10-24 8:57 ` Alan Cox
2008-10-23 1:35 ` [PATCH] n-tty-fix-buffer-full-checks Joe Peterson
2008-10-23 1:35 ` [PATCH] n-tty-output-bells-immediately Joe Peterson
2008-10-24 9:10 ` Alan Cox
2008-10-25 15:41 ` Joe Peterson
2008-10-25 15:48 ` Alan Cox
2008-10-25 15:53 ` Joe Peterson [this message]
2008-10-25 21:13 ` Joe Peterson
2008-10-23 1:36 ` [PATCH] n-tty-fix-buffer-full-gridlock Joe Peterson
2008-10-23 1:56 ` Andrew Morton
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=490340DD.9010605@skyrush.com \
--to=joe@skyrush.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.