On Wed, Nov 8, 2017 at 7:00 AM, Eric Blake wrote:
> On 11/08/2017 08:51 AM, Alistair Francis wrote:
>
> 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
On 11/08/2017 08:51 AM, Alistair Francis wrote:
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__.
On Tue, Nov 7, 2017 at 11:52 PM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> On 11/07/2017 04:12 AM, Markus Armbruster wrote:
>>> Juan Quintela writes:
>>>
Alistair Francis wrote:
> Replace all occurs of __FUNCTION__ except for the check in checkpatch
> with the non GCC spec
Eric Blake writes:
> On 11/07/2017 04:12 AM, Markus Armbruster wrote:
>> Juan Quintela writes:
>>
>>> Alistair Francis wrote:
Replace all occurs of __FUNCTION__ except for the check in checkpatch
with the non GCC specific __func__.
>
+++ b/audio/audio_int.h
@@ -253,7 +
On 11/07/2017 04:12 AM, Markus Armbruster wrote:
> Juan Quintela writes:
>
>> Alistair Francis wrote:
>>> Replace all occurs of __FUNCTION__ except for the check in checkpatch
>>> with the non GCC specific __func__.
>>>
>>> +++ b/audio/audio_int.h
>>> @@ -253,7 +253,7 @@ static inline int audio
Juan Quintela writes:
> Alistair Francis 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
>> Cc: Gerd Hoffmann
>> Cc