public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew-Ztpu424NOJ8@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Dominik Brodowski <linux-JhLEnvuH02M@public.gmane.org>,
	Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC]convert ACPI driver model to Linux driver model -      takes 2
Date: Fri, 14 Oct 2005 06:47:49 -0600	[thread overview]
Message-ID: <20051014124749.GD16113@parisc-linux.org> (raw)
In-Reply-To: <59D45D057E9702469E5775CBB56411F19C4F95@pdsmsx406>

On Fri, Oct 14, 2005 at 05:35:44PM +0800, Li, Shaohua wrote:
> The other issue is some ACPI drivers such as pci_root.c processor.c now
> support hotplug. They require two call backs (.add, .start). The
> callbacks are called in different sequence at the hotplug time and boot
> time. Linux driver model provides .probe callback, so it's hard to
> convert pci_root.c and processor.c.

Why do we need to have devices separately added and started?  What
prevents us from doing it all in one callback?  I can't quite follow
what the current code's doing, much less figure out why it's doing it.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

  reply	other threads:[~2005-10-14 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14  9:35 [RFC]convert ACPI driver model to Linux driver model - takes 2 Li, Shaohua
2005-10-14 12:47 ` Matthew Wilcox [this message]
     [not found]   ` <20051014124749.GD16113-6jwH94ZQLHl74goWV3ctuw@public.gmane.org>
2005-10-18  1:30     ` Shaohua Li
     [not found]       ` <1129599034.3965.6.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-10-18 17:32         ` Rajesh Shah
2005-10-14 15:54 ` Bjorn Helgaas
     [not found]   ` <200510140954.52206.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-10-18  3:06     ` Shaohua Li
  -- strict thread matches above, loose matches on Subject: below --
2005-10-13  8:18 mika.penttila-9Aww8k/80nUxHbG02/KK1g
     [not found] ` <20051013081837.PTGN24578.fep01-app.kolumbus.fi-7B1qVitd7rZYRdgNIgFt/t8DI8KqlI9s@public.gmane.org>
2005-10-13  8:32   ` Shaohua Li
2005-10-13  7:45 Yu, Luming
2005-10-13  8:20 ` Shaohua Li
2005-10-13  6:37 Shaohua Li
     [not found] ` <1129185454.9074.15.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-10-13 20:43   ` Bjorn Helgaas
     [not found]     ` <200510131443.47844.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-10-14  1:13       ` Shaohua Li
     [not found]         ` <1129252436.3948.12.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-10-14  3:21           ` Bjorn Helgaas
2005-10-20 17:04   ` Bjorn Helgaas

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=20051014124749.GD16113@parisc-linux.org \
    --to=matthew-ztpu424noj8@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org \
    --cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-JhLEnvuH02M@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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