From: "Andres Salomon" <dilinger@voxel.net>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.59-mm5
Date: Sat, 25 Jan 2003 03:33:24 -0500 [thread overview]
Message-ID: <pan.2003.01.25.08.33.21.351761@voxel.net> (raw)
In-Reply-To: <20030123195044.47c51d39.akpm@digeo.com>
My atyfb_base.c compile fix (from 2.5.54) still hasn't found its way into
any of the main kernel trees. The original patch generates a reject
against 2.5.59-mm5, so here's an updated patch.
On Thu, 23 Jan 2003 19:50:44 -0800, Andrew Morton wrote:
> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.59/2.5.59-mm5/
>
> . -mm3 and -mm4 were not announced - they were sync-up patches as we
> worked on the I/O scheduler.
>
> . -mm5 has the first cut of Nick Piggin's anticipatory I/O scheduler.
> Here's the scoop:
>
[...]
>
> anticipatory_io_scheduling-2_5_59-mm3.patch
> Subject: [PATCH] 2.5.59-mm3 antic io sched
>
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/
--- a/drivers/video/aty/atyfb_base.c 2003-01-25 03:02:35.000000000 -0500
+++ b/drivers/video/aty/atyfb_base.c 2003-01-25 03:21:48.000000000 -0500
@@ -2587,12 +2587,12 @@
if (info->screen_base)
iounmap((void *) info->screen_base);
#ifdef __BIG_ENDIAN
- if (info->cursor && par->cursor->ram)
+ if (par->cursor && par->cursor->ram)
iounmap(par->cursor->ram);
#endif
#endif
- if (info->cursor)
- kfree(info->cursor);
+ if (par->cursor)
+ kfree(par->cursor);
#ifdef __sparc__
if (par->mmap_map)
kfree(par->mmap_map);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2003-01-25 21:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:50 2.5.59-mm5 Andrew Morton
2003-01-24 11:03 ` 2.5.59-mm5 Alex Bligh - linux-kernel
2003-01-24 11:16 ` 2.5.59-mm5 Andrew Morton
2003-01-24 11:23 ` 2.5.59-mm5 Alex Tomas
2003-01-24 11:50 ` 2.5.59-mm5 Andrew Morton
2003-01-24 12:05 ` 2.5.59-mm5 Alex Tomas
2003-01-24 19:12 ` 2.5.59-mm5 Andrew Morton
2003-01-24 19:58 ` 2.5.59-mm5 Alex Tomas
2003-01-25 17:32 ` 2.5.59-mm5 Ed Tomlinson
2003-01-25 17:41 ` 2.5.59-mm5 Andrew Morton
2003-01-25 20:34 ` 2.5.59-mm5 Ed Tomlinson
2003-01-25 22:33 ` 2.5.59-mm5 Andrew Morton
2003-01-26 1:43 ` 2.5.59-mm5 Ed Tomlinson
2003-01-26 2:17 ` 2.5.59-mm5 Andrew Morton
2003-01-26 3:51 ` 2.5.59-mm5 Ed Tomlinson
2003-01-26 4:04 ` 2.5.59-mm5 Andrew Morton
2003-01-24 15:56 ` 2.5.59-mm5 Oliver Xymoron
2003-01-24 16:04 ` 2.5.59-mm5 Nick Piggin
2003-01-24 17:09 ` 2.5.59-mm5 Giuliano Pochini
2003-01-24 17:22 ` 2.5.59-mm5 Nick Piggin
2003-01-24 19:34 ` 2.5.59-mm5 Valdis.Kletnieks
2003-01-24 20:04 ` 2.5.59-mm5 Jens Axboe
2003-01-24 22:02 ` 2.5.59-mm5 Valdis.Kletnieks
2003-01-25 12:28 ` 2.5.59-mm5 Jens Axboe
2003-01-24 12:14 ` 2.5.59-mm5 Nikita Danilov
2003-01-24 16:00 ` 2.5.59-mm5 Nick Piggin
2003-01-24 11:23 ` 2.5.59-mm5 Jens Axboe
2003-01-24 13:59 ` 2.5.59-mm5 got stuck during boot Helge Hafting
2003-01-24 17:44 ` Ed Tomlinson
2003-01-24 17:56 ` Nick Piggin
2003-01-24 19:18 ` Ed Tomlinson
2003-01-25 8:33 ` Andres Salomon [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=pan.2003.01.25.08.33.21.351761@voxel.net \
--to=dilinger@voxel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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