Hello. Thomas-san. > > This is how it is currently done in memhotplug: > > Driver_register is invoked. There the HID is searched and device pointer > > passed > > if a memory hotplug device is found. > > Then a second search for the same HID (by walk_namespace) is done in > > memhotplug > > and the notify handler is registered for those.
I'd misunderstood for long time. Indeed, I agree it was redundant. I tested your patch on Tiger4 with memory hotplug emulation. It works well. ;-) Thanks. > > BTW: How is this memory hotplugging supposed to work. It only reacts on > > ACPI notifies, my machine > > only has "Check" notify events for mem. What kind of hardware do I need to > > test this and > > how will the eject request be initiated? I don't have any real machine yet. Now, our firmware team is making effort to develop it for our new box. But, Intel might have real box which can use memory hotplug.... Bye. -- Yasunori Goto - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
