> >+#define return_(x) { printk(XENLOG_DEBUG "%s:%d rc: %d\n", \
> >+ __func__,__LINE__, x); return x; }
> >+
.. snip..
> >+ printk(XENLOG_ERR "Could not allocate memory for section table!\n");
>
> Shouldn't this printk be removed if you're using return_?
I was torn on the return_ macro. At one hand it helps to identify what
went wrong with the payload file. But at the same time it is very
developer-centric - so perhaps not to be in the final piece.
And yes, if we do want to go ahead with the return_ macro, then this
should go away.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
