public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Srihari Vijayaraghavan <harisri@bigpond.com>
Subject: 2.4.20pre11aa1
Date: Wed, 16 Oct 2002 18:51:55 +0200	[thread overview]
Message-ID: <20021016165155.GE30254@dualathlon.random> (raw)

Srihari, I would like if you could try to reproduce with this new one
with CONFIG_SOUND=n.  Thanks!

URL:

	http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.20pre11aa1.gz
	http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.20pre11aa1/

Only in 2.4.20pre10aa1: 00_extraversion-10
Only in 2.4.20pre11aa1: 00_extraversion-11
Only in 2.4.20pre10aa1: 00_max_bytes-5
Only in 2.4.20pre11aa1: 00_max_bytes-6
Only in 2.4.20pre10aa1: 60_pagecache-atomic-6
Only in 2.4.20pre11aa1: 60_pagecache-atomic-7
Only in 2.4.20pre10aa1: 70_intermezzo-junk-1
Only in 2.4.20pre11aa1: 70_intermezzo-junk-2

	Rediffed.

Only in 2.4.20pre11aa1: 00_fcntl_getfl-largefile-1

	Clear the implicit O_LARGEPAGE with 64bit archs.

Only in 2.4.20pre11aa1: 00_o_direct-read-overflow-write-locking-xfs-2

	fix xfs compilation (from Christoph).

Only in 2.4.20pre10aa1: 20_sched-o1-fixes-4
Only in 2.4.20pre11aa1: 20_sched-o1-fixes-5

	Take the expired queue into account in sched_yield, still
	sched_yield is a cpu-local operation unlike in 2.4 mainline.

	Fix idle rescheduling so we don't waste an 80% of the cpu power of some
	big irons.

	Fixed a race that could explain some instability (in my my tree only).

Only in 2.4.20pre10aa1: 86_x86_64-tsc-hpet-pit-1

	Dropped temporarily.

Only in 2.4.20pre10aa1: 9900_aio-11.gz
Only in 2.4.20pre11aa1: 9900_aio-12.gz

	Unplug the queue properly in the next_chunk passes too. (from
	Chris Mason)

Andrea

             reply	other threads:[~2002-10-16 16:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 16:51 Andrea Arcangeli [this message]
2002-10-17 12:04 ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 12:10   ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-17 13:01     ` 2.4.20pre11aa1 Keith Owens
2002-10-17 15:26       ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 16:27         ` 2.4.20pre11aa1 Andrea Arcangeli
     [not found]           ` <200210190014.19357.harisri@bigpond.com>
2002-10-18 14:52             ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-18 15:21               ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-18 15:34               ` 2.4.20pre11aa1 Keith Owens
2002-10-18 16:00                 ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-19  1:21                   ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-19  1:25                     ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-22 10:48                       ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-22 14:55                         ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-23 12:27                           ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-23 12:46                             ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-23 14:26                               ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-23 14:35                                 ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-25 14:03                                   ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-31 10:47                                     ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-11-09  9:34                                       ` Solved 2.4.20pre11aa1/2.4.20rc1aa1 Agpgart/Radeon crash. [was: Re: 2.4.20pre11aa1] Srihari Vijayaraghavan
2002-11-10  2:50                                         ` Andrea Arcangeli
2002-11-10  3:24                                           ` Srihari Vijayaraghavan
2002-10-17 13:02     ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 13:00       ` 2.4.20pre11aa1 Andrea Arcangeli

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=20021016165155.GE30254@dualathlon.random \
    --to=andrea@suse.de \
    --cc=harisri@bigpond.com \
    --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