From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: James Simmons <jsimmons@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
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: [Linux-fbdev-devel] Re: [BK fbdev] Yet again more fbdev updates.
Date: Tue, 10 Dec 2002 10:11:10 +0100 [thread overview]
Message-ID: <20021210091110.GA1393@iliana> (raw)
In-Reply-To: <Pine.LNX.4.33.0212091651540.2360-100000@maxwell.earthlink.net>
On Mon, Dec 09, 2002 at 05:04:27PM -0800, James Simmons wrote:
>
> > 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?
>
> Diff against latest BK 2.5.50 tree is at
>
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
Err, could you send also a diff against the 2.5.50 on kernel.org ?
Friendly,
Sven Luther
next prev parent reply other threads:[~2002-12-10 9:11 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
2002-12-10 1:04 ` James Simmons
2002-12-10 9:11 ` Sven Luther [this message]
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=20021210091110.GA1393@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=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.