mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@tv-sign.ru>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	James.Bottomley@hansenpartnership.com, paulus@samba.org,
	davem@davemloft.net, lethal@linux-sh.org, davidm@hpl.hp.com,
	schwidefsky@de.ibm.com, takata@linux-m32r.org, ak@suse.de,
	rth@twiddle.net, matthew@wil.cx
Subject: Re: [patch] fix sparc64 cpu_idle()
Date: Thu, 30 Dec 2004 19:31:14 +0300	[thread overview]
Message-ID: <41D42D52.A459CA25@tv-sign.ru> (raw)
In-Reply-To: <2cd57c9004122911073dea0d2c@mail.gmail.com>

Coywolf Qi Hunt wrote:
> 
> It's not flexible to enforce  'void cpu_idle(void)'  all over. What If
> someday someone would want  to return value for some arch.
> 

May be you are right, but i can't imagine what could be done
after return from cpu_idle() except panic(). cpu_idle() is the
last call in start_kernel().

Oleg.

  parent reply	other threads:[~2004-12-30 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-27 16:10 [PATCH] fix conflicting cpu_idle() declarations Oleg Nesterov
2004-12-27 16:08 ` William Lee Irwin III
2004-12-29 19:07   ` [patch] fix sparc64 cpu_idle() Coywolf Qi Hunt
2004-12-29 19:52     ` Coywolf Qi Hunt
2004-12-29 22:56       ` Mitchell Blank Jr
2004-12-30 16:31     ` Oleg Nesterov [this message]
2004-12-28  2:55 ` [PATCH] fix conflicting cpu_idle() declarations Hirokazu Takata
2004-12-28  3:09   ` William Lee Irwin III
2004-12-28  3:48 ` James Bottomley

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=41D42D52.A459CA25@tv-sign.ru \
    --to=oleg@tv-sign.ru \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=coywolf@gmail.com \
    --cc=davem@davemloft.net \
    --cc=davidm@hpl.hp.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=paulus@samba.org \
    --cc=rth@twiddle.net \
    --cc=schwidefsky@de.ibm.com \
    --cc=takata@linux-m32r.org \
    --cc=wli@holomorphy.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