From: Andrew Morton <akpm@linux-foundation.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] rename thread_info to stack
Date: Wed, 2 May 2007 21:27:21 -0700 [thread overview]
Message-ID: <20070502212721.5883abbc.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705010210010.1479@scrub.home>
On Tue, 1 May 2007 02:10:34 +0200 (CEST) Roman Zippel <zippel@linux-m68k.org> wrote:
> This finally renames the thread_info field in task structure to stack,
> so that the assumptions about this field are gone and archs have more
> freedom about placing the thread_info structure.
It's been a year or so and I've forgotten what the actual point to these
changes is. Can we be reminded please?
next prev parent reply other threads:[~2007-05-03 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 0:10 [PATCH 2/2] rename thread_info to stack Roman Zippel
2007-05-03 4:27 ` Andrew Morton [this message]
2007-05-03 10:52 ` Roman Zippel
2007-05-03 21:19 ` Andrew Morton
2007-05-03 21:38 ` Andi Kleen
2007-05-03 21:45 ` Roman Zippel
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=20070502212721.5883abbc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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