From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] radeonfb update (new patch)
Date: Thu, 03 Feb 2005 17:38:10 +1100 [thread overview]
Message-ID: <1107412690.2362.33.camel@gaston> (raw)
In-Reply-To: <20050202222729.72ad31d4.akpm@osdl.org>
On Wed, 2005-02-02 at 22:27 -0800, Andrew Morton wrote:
> I don't think Linus _can_ apply it - he doesn't have
> try_acquire_console_sem() for a start.
Right, that's a pre-req.
> I currently have:
>
> add-try_acquire_console_sem.patch
> update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch
> radeonfb-massive-update-of-pm-code.patch
> radeonfb-build-fix.patch
>
> And the patch which you've just send replaces
> radeonfb-massive-update-of-pm-code.patch.
Yes.
> Please confirm that all four are needed.
>
> Are you seriously proposing this for 2.6.11??
Well... There should be no problem with
add-try_acquire_console_sem.patch and
update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch.
radeonfb is another story, but the newer patch is definitely less
invasive. It really just fixes bugs and adds the bulk of PM stuff to
wakeup the newer chips, plus some backlight changes. It's been tested by
pmac users for a while, the only reason I sent it to you only recently
is that i was away for a month !
I'm hesitating about having it in 2.6.11 tho due to linus wanting to
release real soon, I'd rather have a bit more non-ppc testing just in
case though... but now it depends entirely on when linus plans to get
2.6.11 out of the door.
Ben.
next prev parent reply other threads:[~2005-02-03 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1107411557.2189.24.camel@gaston>
2005-02-03 6:27 ` [PATCH] radeonfb update (new patch) Andrew Morton
2005-02-03 6:38 ` Benjamin Herrenschmidt [this message]
2005-02-03 8:11 ` Arkadiusz Miskiewicz
2005-02-03 22:25 ` 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=1107412690.2362.33.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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