On Mon, Nov 22, 2010 at 03:13:24PM -0500, Len Brown wrote: > Per the comments from Andrew and others, the concept of a > "full tools build" doesn't actually exit (yet). > > So I guess the only assurance that somebody not on x86 would run > make in this directory this utility lives in tools/power/x86/ > > Note that there are other utilities under tools > which have no Makefile at all... I suspect this will need to be fixed at some point. e.g. kernel rpms probably don't want to hard code all of this but just call some standard make file target. And the kernel eventually needs a make install_user or similar. > > > ...I would prefer a manpage > > I'll be happy to write a manpage. > Is there good example I should follow? Just pick one from /usr/share/man. You can grep for my name if you want one written by me, but I don't claim they are necessarily better than others @) > I'm not inclined to bother, as the use-case for this utility > is to be invoked by another program, and the options available What other program? I could well imagine administrators sticking this into their boot.locals to set the policy they want. > In the highly unlikely scenario that somebody uses > the -r option to excerise the read-only code, > and simultaneously invokes and completes a cpu hot remove FWIW there are setups where core offlining can happen automatically in response to an error. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
