is it worth to add a CLK_REGISTERED flag here? Up to now clocks do nothave to be registered at all and the registering might be forgotten forsome clocks. I suppose funny things can happen when we operate onunregistered clocks.

This implicitely requires that we never register a clock before itsparent is registered. This makes perfect sense but I think we shouldcatch it here when the user tries to register a clock with a not yetregistered parent.

> +> +> + return clk;> +}> +EXPORT_SYMBOL_GPL(clk_register);

BTW we planned to let the linker do the job of registering staticclocks, but this is only convenience and can be added later.