From: Christoph Hellwig <hch@infradead.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [BK fbdev] Yet again more fbdev updates.
Date: Mon, 9 Dec 2002 23:37:49 +0000 [thread overview]
Message-ID: <20021209233749.A8008@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0212091621180.2360-100000@maxwell.earthlink.net>; from jsimmons@infradead.org on Mon, Dec 09, 2002 at 04:23:08PM -0800
On Mon, Dec 09, 2002 at 04:23:08PM -0800, James Simmons wrote:
>
> Hi Linus!!!
>
> Here are the fbdev updates people have so been waiting for. Several
> drivers have been ported. Many fixes have been implemented and many nice
> features have been added as well. Please pull the changes. They have been
> tested by people on this list. Thank you.
>
> bk://fbdev.bkbits.net/fbdev-2.5
Linus,
any chance you could pull James' updates? He has been sending fbdev updates
that fix known issues with many drivers for a long time but I can't even
remember when you merged it the last time. Most fbdev drivers are pretty
unusable in mainline without his fixes.
James,
could you please provide diffstat output, bk changes -L output and a
unified diff for review of the actual changes?
next prev parent reply other threads:[~2002-12-09 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 0:23 [BK fbdev] Yet again more fbdev updates James Simmons
2002-12-09 23:37 ` Christoph Hellwig [this message]
2002-12-10 1:04 ` James Simmons
2002-12-10 9:11 ` [Linux-fbdev-devel] " Sven Luther
2002-12-13 21:50 ` Linus Torvalds
2002-12-14 0:01 ` James Simmons
2002-12-14 0:14 ` Linus Torvalds
2002-12-14 1:49 ` James Simmons
2002-12-14 1:49 ` James Simmons
2002-12-14 1:11 ` Linus Torvalds
2002-12-14 1:11 ` Linus Torvalds
2002-12-14 23:08 ` James Simmons
2002-12-14 0:34 ` James Simmons
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=20021209233749.A8008@infradead.org \
--to=hch@infradead.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.