On Wed, Oct 27, 2010 at 09:14:09AM -0300, Davidlohr Bueso wrote:
> Fair enough. I ran into this when looking to use the xalloc stuff, so we
> just might want to change cpuset_alloc() to use xmalloc instead of
> malloc and be done with it.
No please, we have to thing about stuff in lib/ as about a real library. It
means no fprintf() to stdout/err, no exit on errors (by default). It has
to return error code or NULL on error.
If you want to call exit(), then add extra wrapper cpuset_xalloc().
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
