From owner-freebsd-current Mon Sep 27 13:22:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id EDC32152E0; Mon, 27 Sep 1999 13:22:51 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA31612; Mon, 27 Sep 1999 13:22:50 -0700 (PDT) Date: Mon, 27 Sep 1999 13:22:49 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: Another tty related patch for review/test In-Reply-To: <22216.938461476@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was concerned about the extra checks by devices that have control devices. But a quick sample of drivers indicates that the test for si_tty != NULL catches those. I haven't done an exhaustive test, but it looks like these changes are functionally equivalent to old code assuming that si_tty is corrently preset for all these devices, and NULL for all control devices. (It appears that this is the case.) You have my ok on it.. On Mon, 27 Sep 1999, Poul-Henning Kamp wrote: > > http://phk.freebsd.dk/tty > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message