> > > + * The behavior for zero sized allocs changes. We no longer > > > + * allocate memory but return ZERO_SIZE_PTR. > > > + * WARN so that people can review and fix their code. > > > > I don't see why people have so much opposition to zero-size memory > > allocations. There's all sorts of situations where you want a resizeable > > array that may have zero objects, especially in these days of > > hotpluggability. > > In case you have not read the description to the end: This patch does > exactly what you want and legitimizes zero size object use. The warning > will be remove before 2.6.22 is released.
Ah, sorry then. I just saw this, and remembered a rather contrary discussion about it quite a time ago. Excellent then. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
