All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 2/3] pty: Lock the devpts bits privately
Date: Tue, 08 May 2012 13:41:34 -0700	[thread overview]
Message-ID: <4FA984FE.1040801@zytor.com> (raw)
In-Reply-To: <20120508214309.2d50e5f0@pyramind.ukuu.org.uk>

On 05/08/2012 01:43 PM, Alan Cox wrote:
> 
> One step at a time. I agree entirely that the ideal case is that
> devpts_foo is internally locked and coherent. That is an exercise for
> someone who likes devpts 8)
> 

OK.  I can look at that later; this should detach it enough from the tty
locking that the rest is easy.

	-hpa



  reply	other threads:[~2012-05-08 20:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 21:21 [PATCH 1/3] tty_lock: undo the old tty_lock use on the ctty Alan Cox
2012-05-03 21:22 ` [PATCH 2/3] pty: Lock the devpts bits privately Alan Cox
2012-05-08 18:18   ` H. Peter Anvin
2012-05-08 20:43     ` Alan Cox
2012-05-08 20:41       ` H. Peter Anvin [this message]
2012-05-03 21:24 ` [PATCH 3/3] tty_lock: Localise the lock Alan Cox
2012-05-04 20:48   ` Arnd Bergmann
2012-05-04 23:54   ` Greg KH
2012-05-04 23:55     ` Greg KH
2012-05-07 16:03   ` Sasha Levin
2012-05-07 16:03     ` Sasha Levin
2012-05-07 16:11     ` Alan Cox
2012-05-07 16:30       ` Sasha Levin
2012-05-07 16:42         ` Alan Cox
2012-05-07 17:00           ` Sasha Levin
2012-05-07 21:04             ` Jiri Slaby
2012-05-08 18:12               ` Sasha Levin
2012-05-11 10:40                 ` Sasha Levin
2012-05-11 14:52                   ` Greg KH
2012-05-11 15:09                     ` Sasha Levin
2012-05-11 15:09                       ` Sasha Levin

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=4FA984FE.1040801@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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.