From: Alan Cox <alan@redhat.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Alan Cox <alan@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: PATCH: tty locking for 2.6.9rc2
Date: Wed, 15 Sep 2004 16:40:28 -0400 [thread overview]
Message-ID: <20040915204028.GA25740@devserv.devel.redhat.com> (raw)
In-Reply-To: <1095279799.2958.11.camel@deimos.microgate.com>
On Wed, Sep 15, 2004 at 03:23:19PM -0500, Paul Fulghum wrote:
> Here is a patch against your last patch that clears
> up both the per tty refcount initialization and
> the remove_dev() global refcount leak.
Thanks
> /* Now set up the new line discipline. */
> tty->ldisc = *ld;
> + tty->ldisc.refcount = 0;
What do you think about
tty_ldisc_get(tty, ldisc_num)
That seems to remove the whole mess ?
next prev parent reply other threads:[~2004-09-15 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 16:34 PATCH: tty locking for 2.6.9rc2 Alan Cox
2004-09-15 16:26 ` Paul Fulghum
2004-09-15 16:30 ` Alan Cox
2004-09-15 18:54 ` Paul Fulghum
2004-09-15 20:08 ` Alan Cox
2004-09-15 20:23 ` Paul Fulghum
2004-09-15 20:40 ` Alan Cox [this message]
2004-09-15 20:53 ` Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 0:36 Ulisses
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=20040915204028.GA25740@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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