Juan Quintela <[email protected]> writes: > Alistair Francis <[email protected]> wrote: >> Replace all occurs of __FUNCTION__ except for the check in checkpatch >> with the non GCC specific __func__. >> >> One line in hcd-musb.c was manually tweaked to pass checkpatch. >> >> Signed-off-by: Alistair Francis <[email protected]> >> Cc: Gerd Hoffmann <[email protected]> >> Cc: Andrzej Zaborowski <[email protected]> >> Cc: Stefano Stabellini <[email protected]> >> Cc: Anthony Perard <[email protected]> >> Cc: John Snow <[email protected]> >> Cc: Aurelien Jarno <[email protected]> >> Cc: Yongbok Kim <[email protected]> >> Cc: Peter Crosthwaite <[email protected]> >> Cc: Stefan Hajnoczi <[email protected]> >> Cc: Fam Zheng <[email protected]> >> Cc: Juan Quintela <[email protected]> >> Cc: "Dr. David Alan Gilbert" <[email protected]> >> Cc: [email protected] >> Cc: [email protected] >> Cc: [email protected] >> Reviewed-by: Eric Blake <[email protected]> >> Reviewed-by: Stefan Hajnoczi <[email protected]> > > Reviewed-by: Juan Quintela <[email protected]> > > >> diff --git a/audio/audio_int.h b/audio/audio_int.h >> index 5bcb1c60e1..543b1bd8d5 100644 >> --- a/audio/audio_int.h >> +++ b/audio/audio_int.h >> @@ -253,7 +253,7 @@ static inline int audio_ring_dist (int dst, int src, int >> len) >> #define AUDIO_STRINGIFY(n) AUDIO_STRINGIFY_(n) >> >> #if defined _MSC_VER || defined __GNUC__ >> -#define AUDIO_FUNC __FUNCTION__ >> +#define AUDIO_FUNC __func__ >> #else >> #define AUDIO_FUNC __FILE__ ":" AUDIO_STRINGIFY (__LINE__) >> #endif > > Unrelated to this patch .... > Do we really support other compilers than msc and gcc?
Let me rephrase the question: do we really support compilers that don't understand __func__? The presence of numerous unconditional uses of __func__ in the tree means the answer is no. Let's replace AUDIO_FUNC by plain __func__.
