From: Herbert Poetzl <herbert@13thfloor.at>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] eliminate CLONE_* duplications
Date: Wed, 21 Sep 2005 17:11:24 +0200 [thread overview]
Message-ID: <20050921151124.GB10137@MAIL.13thfloor.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0509211648240.3743@scrub.home>
On Wed, Sep 21, 2005 at 04:53:51PM +0200, Roman Zippel wrote:
> Hi,
>
> On Wed, 21 Sep 2005, Herbert Poetzl wrote:
>
> > please elaborate _why_ we would want a bunch of
> > additional DEFINE entries in each arch instead of a
> > simple include file?
>
> It's more important to keep related definition together and organize
> them logically, than spreading definitions over zillion header files
> for the only purpose to be usable from asm. If you want to cleanup
> sched.h and properly break it up, please go ahead, but I'm afraid that
> will be a lot more work than adding a few defines to asm-offsets.c.
well, I thought that is what my patch did, so please
could you elaborate on the 'properly' part, as this
might be the missing information here ...
TIA,
Herbert
> bye, Roman
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-09-21 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 9:21 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 [this message]
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
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=20050921151124.GB10137@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®