From: Ari Entlich <atrigent@ccs.neu.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH v2] Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call
Date: Mon, 22 Feb 2010 22:17:06 -0500 (EST) [thread overview]
Message-ID: <21495088.197211266895026487.JavaMail.root@zimbra> (raw)
In-Reply-To: <8748337.196941266894473447.JavaMail.root@zimbra>
----- "Andrew Morton" <akpm@linux-foundation.org> wrote:
> Well, it "should" become easier, but does it? Has anyone patched their
> X server to confirm that this kernel change improves things? I'm
> wondering how this change was tested?
Haha yeah, that's a very good point. I put a note in the first version of this patch that it had been compile tested only... I probably should have put the note in the second version as well. It would probably be a good idea to hold off on committing this anywhere until I actually get it working with X. In fact, maybe it would even be best for you to back it out of the mm tree until it's been "proven", at which point I'll resubmit the patch.
> Is there a plan to get the X server modified to use VT_PROCESS_AUTO?
I am now actively working on that.
Also, sorry about the code style issues. I'm a bit of a noob at this. I will include the style fixes in the next version of the patch.
Ari
next parent reply other threads:[~2010-02-23 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8748337.196941266894473447.JavaMail.root@zimbra>
2010-02-23 3:17 ` Ari Entlich [this message]
[not found] <33024815.144191266590249679.JavaMail.root@zimbra>
2010-02-19 14:37 ` [PATCH v2] Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call Ari Entlich
2010-02-22 22:56 ` 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=21495088.197211266895026487.JavaMail.root@zimbra \
--to=atrigent@ccs.neu.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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