linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kronos@kronoz.cjb.net
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org
Subject: Re: [PATCH] bw2: New framebuffer_alloc API and class_dev changes
Date: Mon, 15 Sep 2003 16:22:33 -0700	[thread overview]
Message-ID: <20030915162233.7eeeaee9.davem@redhat.com> (raw)
In-Reply-To: <20030915194246.GF16370@dreamland.darkstar.lan>

On Mon, 15 Sep 2003 21:42:46 +0200
Kronos <kronos@kronoz.cjb.net> wrote:

> this patch converts driver/video/bw2.c to framebuffer_alloc:

It does not apply to current 2.6.x sources, I get rejects.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-09-15 23:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 19:42 [PATCH] bw2: New framebuffer_alloc API and class_dev changes Kronos
2003-09-15 23:22 ` David S. Miller [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=20030915162233.7eeeaee9.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jsimmons@infradead.org \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).