mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Li Shaohua <shaohua.li@intel.com>
Cc: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	ACPI List <acpi-devel@lists.sourceforge.net>,
	Zwane Mwaikambo <zwane@linuxpower.ca>,
	Len Brown <len.brown@intel.com>
Subject: Re: [ACPI] Re: [RFC 0/6] S3 SMP support with physcial CPU hotplug
Date: Mon, 04 Apr 2005 19:55:27 +1000	[thread overview]
Message-ID: <1112608527.3757.19.camel@desktop.cunningham.myip.net.au> (raw)
In-Reply-To: <1112606651.4194.391.camel@sli10-desk.sh.intel.com>

Hi Li.

On Mon, 2005-04-04 at 19:24, Li Shaohua wrote:
> > so that cpu_up mechanism can handle them?
> If S4 also calls a smp_prepare_cpu, then the patches don't break S4. If
> people don't complain warm boot a CPU is slow, I'd like S4 also use
> smp_prepare_cpu.

So you have some more changes? Can I get a monolithic patch to try, when
you're ready?

Thanks!

Nigel
-- 
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028;  Mob: +61 (417) 100 574

Maintainer of Suspend2 Kernel Patches http://suspend2.net


  parent reply	other threads:[~2005-04-04  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  2:05 Li Shaohua
2005-04-04  2:37 ` Andrew Morton
2005-04-04  2:42   ` Li Shaohua
2005-04-04  2:48     ` Andrew Morton
2005-04-04  2:49       ` Li Shaohua
2005-04-04  8:01         ` [ACPI] " Nigel Cunningham
2005-04-04  8:44           ` Li Shaohua
2005-04-04  9:10             ` Pavel Machek
2005-04-04  9:24               ` Li Shaohua
2005-04-04  9:32                 ` Pavel Machek
2005-04-04  9:55                 ` Nigel Cunningham [this message]
2005-04-04  8:44   ` Pavel Machek
2005-04-04  9:54   ` [ACPI] " Nigel Cunningham
2005-04-04 11:31     ` Pavel Machek
2005-04-04 11:46       ` Nigel Cunningham
2005-04-04 19:42       ` Zwane Mwaikambo

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=1112608527.3757.19.camel@desktop.cunningham.myip.net.au \
    --to=ncunningham@cyclades.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shaohua.li@intel.com \
    --cc=zwane@linuxpower.ca \
    /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®