All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Roland Dreier <rdreier@cisco.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] fbcon: Use persistent allocation for cursor blinking.
Date: Tue, 1 Aug 2006 21:28:52 -0400	[thread overview]
Message-ID: <20060802012852.GD22589@redhat.com> (raw)
In-Reply-To: <44CFFDF1.6030909@gmail.com>

On Wed, Aug 02, 2006 at 09:20:49AM +0800, Antonino A. Daplas wrote:

 > >> A naiive question from someone who knows nothing about this subsystem:
 > >> is there any possibility of concurrent calls into this function, for
 > >> example if there are multiple cursors on a multiheaded system?
 > > 
 > > We don't do console multihead so its basically OK. Moving all the
 > > console globals into a struct so we can have multiple instances would be
 > > a good thing [tm] and it would make sense for the variable to end up in
 > > said structure if it was done.
 > > 
 > 
 > Here's an update. Taking Alan's cue, I just moved the global variables
 > to struct fbcon_ops.

Good job.  Have another..

Signed-off-by: Dave Jones <davej@redhat.com>

		Dave

-- 
http://www.codemonkey.org.uk

  parent reply	other threads:[~2006-08-02  1:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 18:56 use persistent allocation for cursor blinking Dave Jones
2006-08-01 19:15 ` Roland Dreier
2006-08-01 19:31   ` Dave Jones
2006-08-01 22:20   ` Alan Cox
2006-08-02  1:20     ` [PATCH] fbcon: Use " Antonino A. Daplas
2006-08-02  1:28       ` [PATCH RESEND] " Antonino A. Daplas
2006-08-02  1:28       ` Dave Jones [this message]
2006-08-01 22:17 ` use " Alan Cox
2006-08-01 22:39   ` Dave Jones
2006-08-01 23:12     ` Alan Cox
2006-08-05 21:26 ` Pavel Machek
2006-08-06 23:46   ` Antonino A. Daplas

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=20060802012852.GD22589@redhat.com \
    --to=davej@redhat.com \
    --cc=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    /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.