[Fwd: Re: [parisc-linux] real2.S in linux-2.5]

[Rüdiger Scholz]

This is a multi-part message in MIME format.
--------------090204010400080205050000
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

This should go to the mailing list also...

--------------090204010400080205050000
Content-Type: message/rfc822;
 name="Re: [parisc-linux] real2.S in linux-2.5"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Re: [parisc-linux] real2.S in linux-2.5"

Message-ID: <3F13AABB.1030106@hrzpub.tu-darmstadt.de>
Date: Tue, 15 Jul 2003 09:18:19 +0200
From: =?ISO-8859-1?Q?R=FCdiger_Scholz?= <rscholz@hrzpub.tu-darmstadt.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.4) Gecko/20030624
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: Matthew Wilcox <willy@debian.org>
Subject: Re: [parisc-linux] real2.S in linux-2.5
References: <3F12C763.7010305@hrzpub.tu-darmstadt.de> <20030714152317.GI23808@parcelfarce.linux.theplanet.co.uk>
In-Reply-To: <20030714152317.GI23808@parcelfarce.linux.theplanet.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Matthew Wilcox schrieb:

>Done.
>
Thanks.

>
> restore_control_regs:
>-       load32  PA(save_cr_space + (N_SAVED_REGS * REG_SZ)), %r26
>+       load32  PA(save_cr_space+(N_SAVED_REGS*REG_SZ)), %r26
>        POP_CR(%cr15, %r26)
>
>I'm a little annoyed this fix wasn't committed to 2.5 already.  I wonder
>what other bits went into the 2.4 tree without going into 2.5 first?
>
Looking at the mail archive for cvs I found the following checkins this 
month for linux-2.4 which had no similar checkin to linux-2.5. But I 
don't know much about kernel development, so perhaps these changes are 
nonly needed in linux-2.4.

    
http://lists.parisc-linux.org/pipermail/parisc-linux-cvs/2003-July/032783.html
    
http://lists.parisc-linux.org/pipermail/parisc-linux-cvs/2003-July/032788.html

>
>BTW, it's not for gcc-3.3's benefit, but for binutils' benefit.
>
Yes, I know. It was a quick'n'dirty email. ;)



--------------090204010400080205050000--