On 09/28/2012 07:23 PM, Josh Triplett wrote: > On Fri, Sep 28, 2012 at 06:20:06PM -0500, Daniel Santos wrote: >> __linktime_error() does the same thing as __compiletime_error() and is >> only used in bug.h. Since the macro defines a function attribute that >> will cause a failure at compile-time (not link-time), it makes more >> sense to keep __compiletime_error(), which is also neatly mated with >> __compiletime_warning(). >> >> Signed-off-by: Daniel Santos <daniel.santos@xxxxxxxxx> > Why not change bug.h in the same commit? Or alternatively, why not > change it first? I'm still new to this project's development process and wasn't sure if those two changes would be considered lumping multiple changes together or not. So that type of lumping is acceptable then? I certainly wouldn't mind squashing them. > Getting rid of __linktime_error *before* changing its > use in bug.h to __compiletime_error seems wrong. Good point! -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
