From: Dave Jones <davej@suse.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] moving task_struct
Date: Fri, 1 Mar 2002 22:14:59 +0100 [thread overview]
Message-ID: <20020301221459.P7662@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0203012040220.32042-100000@serv> <3C7FEAC9.DDA73021@mandrakesoft.com>
In-Reply-To: <3C7FEAC9.DDA73021@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Fri, Mar 01, 2002 at 03:55:37PM -0500
On Fri, Mar 01, 2002 at 03:55:37PM -0500, Jeff Garzik wrote:
> > The patch below simply moves task_struct into its own header file.
> > This makes thread_info and task_struct indepedent from sched.h and will
> > allows archs to decide themselves the dependencies between these
> > structures.
>
> 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.
Indeedy doody. Roman has a nice set of Ruby scripts, which in
conjunction with acme's dependancy graph scripts make for some
interesting reading.
It's tedious work unraveling some of the dependancies, but it's
paid off quite a bit already. (For a real horror story, see
the raid includes. They pull in an obscene amount of extra
headers 8-)
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-01 21:15 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 [this message]
2002-03-04 11:16 ` Daniel Phillips
2002-03-04 18:50 ` Robert Love
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=20020301221459.P7662@suse.de \
--to=davej@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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