On 10/06/2012 12:42 PM, Borislav Petkov wrote: >> @@ -56,10 +65,3 @@ >> #define __visible __attribute__((externally_visible)) >> #endif >> >> -#if __GNUC_MINOR__ > 0 >> -#define __compiletime_object_size(obj) __builtin_object_size(obj, 0) >> -#endif >> -#if __GNUC_MINOR__ >= 3 && !defined(__CHECKER__) > > This last hunk doesn't apply since mainline has a "4" above instead of > "3". And it has had a "4" since it got added by 4a3127693001c so unless > I'm missing something, how did the 3 appear in your patches? These are based against -mm, where another commit is already in that changes it. I was told that since that commit was already in -mm, to not include it in the patch set: 6c620cf1536a0ce6a83ecaaaf05298dcc0f7d440 (committed 2012-09-27) This was probably (at least partially) the result of the fiasco I had with my email. -- 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
