mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Steve Young <sdyoung@vt220.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] change pts allocation behaviour in
Date: Fri, 7 May 2004 04:14:42 -0700	[thread overview]
Message-ID: <20040507041442.7e67c15e.akpm@osdl.org> (raw)
In-Reply-To: <20040507084242.GA11389@eviltron.local.lan>

Steve Young <sdyoung@vt220.org> wrote:
>
>   Here is a patch to change the way ptses are allocated.  It applies against
>  2.6.6-rc3.  Basically it tries to humour old glibc by always obtaining a pts
>  in the range of 0-255 first.  However, if that fails, then it will search the
>  higher ranges. 

Wouldn't we be better off with plain old first-fit-from-zero?

  parent reply	other threads:[~2004-05-07 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  8:42 Steve Young
2004-05-07  9:48 ` [PATCH] change pts allocation behaviour in tty_io.c, v2 Steve Young
2004-05-07 11:14 ` Andrew Morton [this message]
2004-05-07 11:52   ` [PATCH] change pts allocation behaviour in Steve Young
2004-05-07 19:09     ` Andrew Morton

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=20040507041442.7e67c15e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdyoung@vt220.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

all inboxes | Powered by JetHome®