From: Ben Collins <ben.collins@canonical.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VT: Restore VT fonts on switch
Date: Mon, 21 Jul 2008 17:40:09 -0400 [thread overview]
Message-ID: <1216676409.7585.215.camel@cunning> (raw)
In-Reply-To: <20080721142315.4076c292@infradead.org>
On Mon, 2008-07-21 at 14:23 -0700, Arjan van de Ven wrote:
> On Mon, 21 Jul 2008 16:53:04 -0400
> Ben Collins <bcollins@swissdisk.com> wrote:
>
> > On Mon, 2008-07-21 at 13:43 -0700, Arjan van de Ven wrote:
> > > On Mon, 21 Jul 2008 15:39:44 -0400
> > > Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > >
> > > > Not all X drivers save and restore fonts on text VTs. Add code to
> > > > the kernel to explicitly save and restore them on VT switches.
> > >
> > >
> > > do you have a list of which ones don't ?
> >
> > I don't, but perhaps Matthew does.
> >
> I was assuming Matthew would respond since he sent this patch to lkml
> after all...
Actually, I sent it on Matthews behalf, so perhaps you could understand
why I answered.
next prev parent reply other threads:[~2008-07-21 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 19:39 [PATCH] VT: Restore VT fonts on switch Matthew Garrett
2008-07-21 20:40 ` Alan Cox
2008-08-08 9:32 ` Benjamin Herrenschmidt
2008-07-21 20:43 ` Arjan van de Ven
2008-07-21 20:53 ` Ben Collins
2008-07-21 21:12 ` Alan Cox
2008-07-21 21:37 ` Matthew Garrett
2008-07-21 21:24 ` Alan Cox
2008-08-08 7:49 ` Pavel Machek
2008-07-21 21:23 ` Arjan van de Ven
2008-07-21 21:40 ` Ben Collins [this message]
2008-07-21 22:18 ` Arjan van de Ven
2008-07-21 22:29 ` Ben Collins
2008-07-21 20:54 ` Jan Engelhardt
2008-07-22 7:59 ` Arkadiusz Miskiewicz
2008-08-08 7:44 ` Pavel Machek
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=1216676409.7585.215.camel@cunning \
--to=ben.collins@canonical.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.