All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Vivien Chappelier <vivienc@nerim.net>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 2.5] r4k_switch task_struct/thread_info fixes
Date: Tue, 4 Feb 2003 13:54:31 +0100	[thread overview]
Message-ID: <20030204135431.A29811@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0302032311160.25421-100000@melkor>; from vivienc@nerim.net on Mon, Feb 03, 2003 at 11:21:50PM +0100

On Mon, Feb 03, 2003 at 11:21:50PM +0100, Vivien Chappelier wrote:

> 	This patch fixes an incorrect use of THREAD_FLAGS instead of
> TI_FLAGS when clearing the TIF_USEDFPU flag of the current thread info,
> and an incorrect assumption when using ST_OFF, that the stack is shared
> with task_struct, whereas it is shared with thread_info in 2.5.

Ok.  You missed r2300_switch.S though :)

  Ralf

  reply	other threads:[~2003-02-04 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 22:21 [PATCH 2.5] r4k_switch task_struct/thread_info fixes Vivien Chappelier
2003-02-04 12:54 ` Ralf Baechle [this message]
2003-02-07  0:36 ` Jun Sun
2003-02-07  9:29   ` Vivien Chappelier
2003-02-07 18:40     ` Jun Sun

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=20030204135431.A29811@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=vivienc@nerim.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.