public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Bernat <bernat@free.fr>
To: Shawn Starr <spstarr@sh0n.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT: 2.4.19-pre2-ac2-xfs-shawn9 released
Date: Wed, 06 Mar 2002 09:45:02 +0100	[thread overview]
Message-ID: <m3vgcakru9.fsf@neo.loria> (raw)
In-Reply-To: <Pine.LNX.4.40.0203052117390.278-100000@coredump.sh0n.net>
In-Reply-To: <Pine.LNX.4.40.0203052117390.278-100000@coredump.sh0n.net> (Shawn Starr's message of "Tue, 5 Mar 2002 21:18:20 -0500 (EST)")

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

OoO En ce milieu de nuit étoilée du mercredi 06 mars 2002, vers 03:18,
Shawn Starr <spstarr@sh0n.net> disait:

> What change did you have to make with rml's patch? Some people are
> wondering. I haven't tried it yet.

A very trivial change, I have just merged this one by hand :

***************
*** 318,323 ****
  	unsigned long policy;
  	unsigned long cpus_allowed;
  	unsigned int time_slice;
  
  	task_t *next_task, *prev_task;
  
--- 322,328 ----
  	unsigned long policy;
  	unsigned long cpus_allowed;
  	unsigned int time_slice;
+ 	unsigned long flags;
  
  	task_t *next_task, *prev_task;
  
Otherwise, the patch apply cleanly.
I attach you the corrected patch (I don't knwo why, it is
significiantly larger than the original patch, I have used diff -Naur,
I hope I don't get lost when I did it, it is surely better to use the
original patch and to do the little merge by hand)


[-- Attachment #2: Patch for preempt --]
[-- Type: application/octet-stream, Size: 51294 bytes --]

[-- Attachment #3: Type: text/plain, Size: 102 bytes --]

-- 
 /*
  * We used to try various strange things. Let's not.
  */
	2.2.16 /usr/src/linux/fs/buffer.c

  reply	other threads:[~2002-03-06  8:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10  2:36 ANNOUNCEMENT: XFS patches with rmap12d + 2.4.18-pre9 + Shawn Starr
2002-02-17  8:36 ` ANNOUNCEMENT: 2.4.18-rc1-xfs-shawn5 released Shawn Starr
2002-02-17 22:26   ` ANNOUNCEMENT: 2.4.18-rc1-xfs-shawn6 released Shawn Starr
2002-02-28  1:52     ` ANNOUNCEMENT: 2.4.19-pre1-ac1-xfs-shawn7 released Shawn Starr
2002-02-28  1:54       ` ANNOUNCEMENT: 2.4.19-pre1-ac1-xfs-shawn7 released - more Shawn Starr
2002-02-28  3:59         ` ANNOUNCEMENT: 2.4.19-pre1-ac2-xfs-shawn8 released Shawn Starr
2002-02-28  4:48           ` ANNOUNCEMENT: 2.4.19-pre1-ac2-xfs-shawn8 released - important Shawn Starr
2002-03-05  7:24             ` ANNOUNCEMENT: 2.4.19-pre2-ac2-xfs-shawn9 released Shawn Starr
2002-03-05  7:32               ` Shawn Starr
2002-03-05  7:44               ` Shawn Starr
2002-03-11  8:54                 ` ANNOUNCEMENT: 2.4.19-pre2-ac4-xfs-shawn10 released Shawn Starr
2002-03-05 16:44               ` ANNOUNCEMENT: 2.4.19-pre2-ac2-xfs-shawn9 released Vincent Bernat
2002-03-06  2:18                 ` Shawn Starr
2002-03-06  8:45                   ` Vincent Bernat [this message]
2002-03-06 18:59                   ` Bill Davidsen

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=m3vgcakru9.fsf@neo.loria \
    --to=bernat@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spstarr@sh0n.net \
    /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