From: Andrew Morton <akpm@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org, ajoshi@shell.unixbox.com,
linux-fbdev-devel@lists.sourceforge.net,
benh@kernel.crashing.org
Subject: Re: Radeon framebuffer weirdness in -mm2
Date: Thu, 20 Jan 2005 16:01:23 -0800 [thread overview]
Message-ID: <20050120160123.14f13ca6.akpm@osdl.org> (raw)
In-Reply-To: <20050120234844.GF12076@waste.org>
Matt Mackall <mpm@selenic.com> wrote:
>
> > Which radeon driver? CONFIG_FB_RADEON_OLD or CONFIG_FB_RADEON?
>
> FB_RADEON.
Ah, OK. Likely culprits are
radeonfb-massive-update-of-pm-code.patch
radeonfb-build-fix.patch
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org, ajoshi@shell.unixbox.com,
linux-fbdev-devel@lists.sourceforge.net,
benh@kernel.crashing.org
Subject: Re: Radeon framebuffer weirdness in -mm2
Date: Thu, 20 Jan 2005 16:01:23 -0800 [thread overview]
Message-ID: <20050120160123.14f13ca6.akpm@osdl.org> (raw)
In-Reply-To: <20050120234844.GF12076@waste.org>
Matt Mackall <mpm@selenic.com> wrote:
>
> > Which radeon driver? CONFIG_FB_RADEON_OLD or CONFIG_FB_RADEON?
>
> FB_RADEON.
Ah, OK. Likely culprits are
radeonfb-massive-update-of-pm-code.patch
radeonfb-build-fix.patch
next prev parent reply other threads:[~2005-01-20 23:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:21 Radeon framebuffer weirdness in -mm2 Matt Mackall
2005-01-20 23:39 ` Andrew Morton
2005-01-20 23:39 ` Andrew Morton
2005-01-20 23:48 ` Matt Mackall
2005-01-21 0:01 ` Andrew Morton [this message]
2005-01-21 0:01 ` Andrew Morton
2005-01-21 3:57 ` Matt Mackall
2005-01-21 4:05 ` Andrew Morton
2005-01-21 4:07 ` Andrew Morton
2005-01-21 4:07 ` Andrew Morton
2005-01-21 6:09 ` Matt Mackall
2005-01-21 12:33 ` Roman Zippel
2005-01-21 16:36 ` Antonino A. Daplas
2005-01-21 16:36 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-01-22 0:52 ` Matt Mackall
2005-01-24 4:00 ` Benjamin Herrenschmidt
2005-01-24 4:00 ` Benjamin Herrenschmidt
2005-01-21 16:36 ` Antonino A. Daplas
2005-01-21 16:36 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-01-21 0:03 ` Benjamin Herrenschmidt
2005-01-21 0:03 ` Benjamin Herrenschmidt
2005-01-21 0:24 ` James Simmons
2005-01-21 0:24 ` [Linux-fbdev-devel] " James Simmons
2005-01-21 0:03 ` Benjamin Herrenschmidt
2005-01-21 0:03 ` Benjamin Herrenschmidt
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=20050120160123.14f13ca6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ajoshi@shell.unixbox.com \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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.