From: Paul Fulghum <paulkf@microgate.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stuart MacDonald <stuartm@connecttech.com>,
"'Oliver Neukum'" <oliver@neukum.org>,
linux-kernel@vger.kernel.org
Subject: Re: question on tty open and close
Date: Wed, 28 Mar 2007 09:32:32 -0600 [thread overview]
Message-ID: <460A8A90.3010401@microgate.com> (raw)
In-Reply-To: <20070328163158.658b372a@the-village.bc.nu>
Alan Cox wrote:
> It breaks if any existing driver is doing no cleanup in ->open() when it
> fails but relying upon ->close() being called. That is what needs
> auditing first of all.
Yes, I did not think of that.
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2007-03-28 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 11:38 question on tty open and close Oliver Neukum
2007-03-28 13:10 ` Stuart MacDonald
2007-03-28 13:16 ` Oliver Neukum
2007-03-28 13:22 ` Stuart MacDonald
2007-03-28 14:44 ` Alan Cox
2007-03-28 15:26 ` Paul Fulghum
2007-03-28 15:31 ` Alan Cox
2007-03-28 14:54 ` Marcel Holtmann
2007-03-28 15:32 ` Paul Fulghum [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-28 14:37 Kilau, Scott
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=460A8A90.3010401@microgate.com \
--to=paulkf@microgate.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stuartm@connecttech.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