linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] eliminate CLONE_* duplications
Date: Tue, 27 Sep 2005 19:04:10 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0509271856430.3728@scrub.home> (raw)
In-Reply-To: <20050927162242.GC21927@MAIL.13thfloor.at>

Hi,

On Tue, 27 Sep 2005, Herbert Poetzl wrote:

> > "logically organized" mainly means reducing dependencies by organizing
> > them by their logical dependencies. 
> 
> did you consider that separating out the clone
> stuff might be that basis for reducing dependencies?

Not in this form, all users of this flag need other definitions from 
sched.h.

> > The hardcoded defines actually do need fixing, frv is especially bad,
> > as it even has hardcoded structure offsets.
> 
> so instead of fixing the issue properly, we 
> 'mend' it by adding new code to */asm-offsets.c

Using asm-offsets.c _is_ a proper solution.

> > sched.h is especially challenging due to dependencies between headers
> > under asm and linux. It's not just splitting sched.h, it also requires
> > analyzing its dependencies.
> 
> which you obviously think is nothing I can do
> 'properly' ...

I don't know, but I know that it does require a large amount of experience 
in this area.

bye, Roman

      reply	other threads:[~2005-09-27 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21  9:21 [Patch] eliminate CLONE_* duplications Herbert Poetzl
2005-09-21 10:55 ` Roman Zippel
2005-09-21 14:39   ` Herbert Poetzl
2005-09-21 14:53     ` Roman Zippel
2005-09-21 15:11       ` Herbert Poetzl
2005-09-21 15:39         ` Roman Zippel
2005-09-21 23:58           ` Herbert Poetzl
2005-09-27 15:25             ` Roman Zippel
2005-09-27 16:22               ` Herbert Poetzl
2005-09-27 17:04                 ` Roman Zippel [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=Pine.LNX.4.61.0509271856430.3728@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=akpm@osdl.org \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).