linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Jean Delvare <khali@linux-fr.org>,
	James Simmons <jsimmons@users.sf.net>,
	Antonino Daplas <adaplas@pol.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] FB: Possible fbcon cleanups
Date: Mon, 10 Jan 2005 05:16:08 +0800	[thread overview]
Message-ID: <200501100516.08056.adaplas@hotpop.com> (raw)
In-Reply-To: <20041226151351.32608309.khali@linux-fr.org>

On Sunday 26 December 2004 22:13, Jean Delvare wrote:
> Hello,
>
> While browsing the video/fbcon.c source file (Linux 2.6.10-rc3) I found
> some possible cleanups. Patch follows, feel free to apply all or parts
> of it if it looks OK to you.
>

Looks good, thanks.

Tony

      reply	other threads:[~2005-01-09 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-26 14:13 [PATCH 2.6] FB: Possible fbcon cleanups Jean Delvare
2005-01-09 21:16 ` Antonino A. Daplas [this message]

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=200501100516.08056.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=jsimmons@users.sf.net \
    --cc=khali@linux-fr.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).