From: Ari Entlich <atrigent@ccs.neu.edu>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 34/36] tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call
Date: Tue, 2 Mar 2010 18:55:20 -0500 (EST) [thread overview]
Message-ID: <12806278.317911267574120161.JavaMail.root@zimbra> (raw)
In-Reply-To: <14018832.317861267574035528.JavaMail.root@zimbra>
Hello!
Could you please remove this patch from your 2.6.34 tty pull request?
Andrew Morton questioned whether this should actually be used yet[1],
and I responded confirming his suspicions[2]. In addition, this patch
has not "been in the linux-next and -mm releases for a number of
weeks now", as you suggest in your pull request.
Thanks!
[1] http://marc.info/?l=linux-kernel&m=126687954823617
[2] http://marc.info/?l=linux-kernel&m=126689506608539
----- "Greg Kroah-Hartman" <gregkh@suse.de> wrote:
> From: Ari Entlich <atrigent@ccs.neu.edu>
>
> This new VT mode (VT_PROCESS_AUTO) does everything that VT_PROCESS does
> except that it doesn't wait for a VT_RELDISP ioctl before switching
> away from a VT with that mode.
>
> [etc, etc...]
next parent reply other threads:[~2010-03-02 23:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14018832.317861267574035528.JavaMail.root@zimbra>
2010-03-02 23:55 ` Ari Entlich [this message]
2010-03-03 0:02 ` [PATCH 34/36] tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call Greg KH
[not found] <455171.511691268697128244.JavaMail.root@zimbra>
2010-03-15 23:53 ` Ari Entlich
2010-03-16 0:18 ` Greg KH
[not found] <9842632.318001267575211703.JavaMail.root@zimbra>
2010-03-03 0:16 ` Ari Entlich
2010-03-15 20:33 ` Greg KH
2010-03-02 23:09 [GIT PATCH] TTY patches for 2.6.33-git Greg KH
2010-03-02 23:36 ` [PATCH 34/36] tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call Greg Kroah-Hartman
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=12806278.317911267574120161.JavaMail.root@zimbra \
--to=atrigent@ccs.neu.edu \
--cc=gregkh@suse.de \
--cc=linux-kernel@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.