From: "David S. Miller" <davem@redhat.com>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: sparclinux@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org
Subject: Re: [PATCH] sbusfb: Initialize cmap.transp in FBIOPUTCMAP_SPARC
Date: Sun, 6 Jun 2004 19:58:58 -0700 [thread overview]
Message-ID: <20040606195858.6fe4c75e.davem@redhat.com> (raw)
In-Reply-To: <20040606010629.A23517@mail.kroptech.com>
On Sun, 6 Jun 2004 01:06:29 -0400
Adam Kropelin <akropel1@rochester.rr.com> wrote:
> When handling FBIOPUTCMAP_SPARC, sbusfb fails to initialize cmap.transp,
> which quickly leads to an oops when fb_set_cmap() dereferences it.
>
> First encountered in Aurora Wombat kernels and seems to afflict mainline
> as well. Patch is against 2.6.7-rc2. xorg still fails to actually get
> anything to display on my CG6, but at least it no longer oopses the kernel.
>
> Signed-off-by: Adam Kropelin <akropel1@rochester.rr.com>
Applied, thanks a lot Adam.
prev parent reply other threads:[~2004-06-07 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 5:06 [PATCH] sbusfb: Initialize cmap.transp in FBIOPUTCMAP_SPARC Adam Kropelin
2004-06-07 2:58 ` 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=20040606195858.6fe4c75e.davem@redhat.com \
--to=davem@redhat.com \
--cc=akropel1@rochester.rr.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sparclinux@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).