public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Owen <owen@cus.org.uk>
To: glen.turner@aarnet.edu.au
Cc: linux-kernel@vger.kernel.org
Subject: Linux serial console patch
Date: Sun, 5 Sep 2004 18:24:36 +0100 (BST)	[thread overview]
Message-ID: <20040905175037.O58184@cus.org.uk> (raw)

Glen Turner,

I have read your posts to lkml containing your serial console flow control
patches firstly for 2.4.x and then for 2.6.x kernels.

Rationale:
 "[PATCH] 0/3 Fix serial console flow control"
    http://www.ussg.iu.edu/hypermail/linux/kernel/0210.1/1790.html
2.4 patches:
 "[PATCH] 1/3 Fix serial console flow control, serial.c"
    http://www.ussg.iu.edu/hypermail/linux/kernel/0210.1/1791.html
 "[PATCH] 2/3 Fix serial console flow control, serialP.h"
    http://www.ussg.iu.edu/hypermail/linux/kernel/0210.1/1792.html
 "[PATCH] 3/3 Fix serial console flow control, serial-console.txt"
    http://www.ussg.iu.edu/hypermail/linux/kernel/0210.1/1793.html
2.6 patch:
 "[PATCH] Fix CTS/RTS flow control in serial console"
    http://www.ussg.iu.edu/hypermail/linux/kernel/0310.2/1080.html

I have not been able to find any feedback on those patches in the lkml
archives. Also I can find no evidence that the patch made it into the
2.6.8.1 kernel. This is a shame as I found your rationale very
persuasive.

Do you maintain an up-to-date version of this patch?
Did you get any feedback for this patch, positive or negative?
Do you need people (i.e. me) to test this patch?

Thanks
Alex Owen

             reply	other threads:[~2004-09-05 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 17:24 Alex Owen [this message]
2004-09-05 23:38 ` Linux serial console patch James Courtier-Dutton
2004-09-06 10:32   ` Danny ter Haar
2004-09-06 10:43     ` Russell King
2004-09-06 15:45       ` James Courtier-Dutton
2004-09-06 15:52         ` Russell King
2004-09-06 16:46           ` Randy.Dunlap
2004-09-11 20:58             ` Herbert Poetzl

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=20040905175037.O58184@cus.org.uk \
    --to=owen@cus.org.uk \
    --cc=glen.turner@aarnet.edu.au \
    --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