From: Robert Love <rml@tech9.net>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Roman Zippel <zippel@linux-m68k.org>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] moving task_struct
Date: 04 Mar 2002 13:50:06 -0500 [thread overview]
Message-ID: <1015267808.15479.16.camel@phantasy> (raw)
In-Reply-To: <E16hqRx-0000cv-00@starship.berlin>
In-Reply-To: <Pine.LNX.4.21.0203012040220.32042-100000@serv> <3C7FEAC9.DDA73021@mandrakesoft.com> <E16hqRx-0000cv-00@starship.berlin>
On Mon, 2002-03-04 at 06:16, Daniel Phillips wrote:
> On March 1, 2002 09:55 pm, Jeff Garzik wrote:
> > nice... In addition to your second patch, this first patch may be a
> > small step in paving the way for further unraveling of nasty include
> > dependencies.
>
> Apropo of that, struct page needs to be defined before mmzone.h is
> included, so that inlines in mmzone.h can do arithmetic involving
> sizeof(struct page), instead of using macros.
Yep.
The preempt patch in 2.4 hit some of the uglies of sched.h. Thankfully,
in 2.5 we use thread_info exclusive and Linus helped me remove all
sched.h dependencies - it is a big cleanup. sched.h and its related and
interrelated dependencies are _not_ pretty.
Anything you do helps, Daniel ;)
Robert Love
prev parent reply other threads:[~2002-03-04 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 20:22 [PATCH] moving task_struct Roman Zippel
2002-03-01 20:55 ` Jeff Garzik
2002-03-01 21:14 ` Dave Jones
2002-03-04 11:16 ` Daniel Phillips
2002-03-04 18:50 ` Robert Love [this message]
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=1015267808.15479.16.camel@phantasy \
--to=rml@tech9.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=torvalds@transmeta.com \
--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