From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: tony.luck@gmail.com, mochel@digitalimplant.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] kill include/linux/platform.h
Date: Mon, 10 Oct 2005 11:23:41 -0700 [thread overview]
Message-ID: <20051010112341.7bb116ae.akpm@osdl.org> (raw)
In-Reply-To: <20051003215053.GI3652@stusta.de>
Adrian Bunk <bunk@stusta.de> wrote:
>
> On Mon, Oct 03, 2005 at 02:07:12PM -0700, Tony Luck wrote:
> > > The default_idle() prototype should stay inside some header file.
> >
> > That would be best, yes.
> >
> > > @Patrick:
> > > Any suggestion where it should move to?
> >
> > Of the include files already included directly by arch/ia64/kernel/setup.c,
> > <linux/sched.h> looks the most promising. There's lots of .*idle.* things
> > already in there.
> >
> > Looking at existing precedent: ppc64 has a definition of default_idle()
> > in <asm/machdep.h>
>
> The question whether linux/ or asm/ is the best place for the definition
> boils down to the question whether it is expected that default_idle() is
> present on all architectures or whether it's an architecture-specific
> implementation detail.
Yes, default_idle() is arch-specific and so its prototype should be in an
arch-specific header.
All the implementations happen to have the same signature, so it's tempting
to put the prototype into some generic header, but given that there's no
non-arch-specific caller, we shouldn't do that.
next prev parent reply other threads:[~2005-10-10 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 20:52 2.6: is include/linux/platform.h a dead header? Adrian Bunk
[not found] ` <Pine.LNX.4.50.0509291106520.29808-100000@monsoon.he.net>
2005-10-01 23:34 ` [2.6 patch] kill include/linux/platform.h Adrian Bunk
2005-10-03 19:01 ` Tony Luck
2005-10-03 19:03 ` Adrian Bunk
2005-10-03 21:07 ` Tony Luck
2005-10-03 21:50 ` Adrian Bunk
2005-10-10 18:23 ` Andrew Morton [this message]
2005-11-03 18:23 ` Adrian Bunk
2005-11-08 19:46 ` Patrick Mochel
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=20051010112341.7bb116ae.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=tony.luck@gmail.com \
/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
Powered by JetHome