All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] moving task_struct
Date: Fri, 01 Mar 2002 15:55:37 -0500	[thread overview]
Message-ID: <3C7FEAC9.DDA73021@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0203012040220.32042-100000@serv>

> 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.

Regards,

	Jeff



-- 
Jeff Garzik      |
Building 1024    |
MandrakeSoft     | Choose life.

  reply	other threads:[~2002-03-01 20:56 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 [this message]
2002-03-01 21:14   ` Dave Jones
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=3C7FEAC9.DDA73021@mandrakesoft.com \
    --to=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 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.