From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.8pre3aa1
Date: Thu, 2 Aug 2001 17:30:58 +0200 [thread overview]
Message-ID: <20010802173058.C24436@athlon.random> (raw)
diff between 2.4.7aa1 and 2.4.8pre3aa1 (besides moving on top of
2.4.8pre3aa1). Possibly the vm is screwedup in 2.4.8pre3 so 2.4.8pre3aa1
could behave very badly too (possibly the blkdev in pagecache could hide
problems with the buffercache so please make sure to stress the
buffercache with fs fs metadata too).
Only in 2.4.8pre3aa1: 00_backout-local_bh_enable-debug-1
Drop some leftover. However I recommend all people with the aic driver
to apply my debugging patch that I posted to l-k in reply to Alexey and
to fix the bug instead of hiding and forgetting it (smp_call_function
*must* be recalled with irq enabled!!!).
Only in 2.4.7aa1: 00_free_shortage-bool-1
Dropped, it was a minor optimization and it rejected with some vm
update.
Only in 2.4.8pre3aa1: 00_gcc-30-aironet-1
Only in 2.4.7aa1: 00_gcc-30-extern-static-1
Only in 2.4.8pre3aa1: 00_gcc-30-extern-static-2
Only in 2.4.7aa1: 00_gcc-30-reiserfs-1
Some s/extern/static/ merged in mainline so dropped or updated the
rest.
Only in 2.4.7aa1: 00_ircomm-t39m-1
Only in 2.4.7aa1: 00_max_readahead-1
Only in 2.4.7aa1: 00_net_rx_softirq-optimize-1
Only in 2.4.7aa1: 00_softirq-fixes-5
Merged in mainline.
Only in 2.4.7aa1: 00_o_direct-10
Only in 2.4.8pre3aa1: 00_o_direct-11
Bugfix from Ken to update the inode size correctly.
Only in 2.4.8pre3aa1: 00_softirq-fixes-6_wait-network-fixes-1
Workaround the fact not all netif_rx callers know they have to run
do_softirq() if they run in normal kernel context (will be dropped as
soon as the lowlevel drivers learnt that in mainline, this is just a
*very* temporary thing).
Only in 2.4.7aa1: 40_blkdev-pagecache-7
Only in 2.4.8pre3aa1: 40_blkdev-pagecache-8
Move to 1k granularity to be backwards compatible. Some other backwards
compatible change like ignoring O_APPEND to workaround buggy programs.
Only in 2.4.7aa1: 30_tux
Only in 2.4.8pre3aa1: 60_atomic-alloc-3
Only in 2.4.8pre3aa1: 60_atomic-lookup-4
Only in 2.4.8pre3aa1: 60_net-exports-1
Only in 2.4.8pre3aa1: 60_pagecache-atomic-1
Only in 2.4.8pre3aa1: 60_tux-3
Only in 2.4.8pre3aa1: 60_tux-data-1
Only in 2.4.8pre3aa1: 60_tux-dprintk-1
Only in 2.4.8pre3aa1: 60_tux-exports-1
Only in 2.4.8pre3aa1: 60_tux-kstat-2
Only in 2.4.8pre3aa1: 60_tux-process-1
Only in 2.4.8pre3aa1: 60_tux-syscall-1
Only in 2.4.8pre3aa1: 60_tux-sysctl-2
Only in 2.4.8pre3aa1: 60_tux-vfs-2
Only in 2.4.8pre3aa1: 61_tux-logger-1
Only in 2.4.8pre3aa1: 62_tux-uml-1
Tux moved out of the separate directory and applied as last thing.
Andrea
reply other threads:[~2001-08-02 15:30 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=20010802173058.C24436@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
all inboxes | Powered by JetHome®