From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.6pre3aa2
Date: Wed, 20 Jun 2001 15:44:30 +0200 [thread overview]
Message-ID: <20010620154430.D22569@athlon.random> (raw)
Diff between 2.4.6pre3aa1 and 2.4.6pre3aa2:
Only in 2.4.6pre3aa2: 00_alpha-numa-initrd-1
Release initrd memory from right numa node.
(recommended)
Only in 2.4.6pre3aa2: 00_alpha-srm-2.4.6-pre1-1
Access the srm variables via /proc/srm_environment.
Patch posted to l-k by Jan-Benedict Glaw <jbglaw@lug-owl.de>.
(nice to have)
Only in 2.4.6pre3aa2: 00_initrd-release-blkdev-1
Remeber to release the opened blkdev after initrd load.
(recommended)
Only in 2.4.6pre3aa2: 00_ksoftirqd-6_ia64-1
Only in 2.4.6pre3aa2: 00_ksoftirqd-6_ppc-1
softirq updates for ppc and ia64.
(recommended)
Only in 2.4.6pre3aa2: 00_locks-1
Fix from ac16 (avoid corrupting the lock_depth).
(recommended)
Only in 2.4.6pre3aa2: 00_max-threads-1
Each task is going to take more than 2 pages. There's
also the pid limit and the per-user limit but turning
the default down is good idea. Fix from Rik from ac16.
(recommended)
Only in 2.4.6pre3aa2: 00_swapinfo-1
Only show deviecs when then swap_map is been allocated
to avoid oops during swapon. Fix from
Paul Menage <pmenage@ensim.com>.
(nice to have)
Only in 2.4.6pre3aa1/30_tux: 30_atomic-lookup-3
Only in 2.4.6pre3aa2/30_tux: 30_atomic-lookup-4
Introduce O_ATOMICLOOKUP for ppc equal to 01000000.
Only in 2.4.6pre3aa2: 40_experimental/40_blkdev-pagecache-3
Optional patch to apply to move the blkdev from buffercache to
pagecache. At the moment this breaks the ramdisk and in turn initrd.
Read the 40_experimental/README for more details. Like the tux patches
this one is not included into the global diff (2.4.6pre3aa2.{gz,bz2}).
Andrea
reply other threads:[~2001-06-20 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010620154430.D22569@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@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