From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 24 Apr 2020 00:54:30 GMT
Subject: Re: [PATCH 1/4] C: s/0/NULL/ for pointer type
Message-ID: <xmqqd07xem9l.fsf@gitster.c.googlers.com>
In-Reply-To: <1df91aa4-dda5-64da-6ae3-5d65e50a55c5@ramsayjones.plus.com>

Ramsay Jones <ramsay@ramsayjones.plus.com> writes:

> Actually, I have a patch somewhere which suppressed the sparse warning
> for the '= { 0 }' token sequence used in these initializations. However,
> I don't seem to be able to find them at the moment! :(

AHHHHHhhhhhhhh.  

Thanks for reminding.  Yeah, I recall that the concensus of those
who were vocal in that old discussion [*1*] was that "= { 0 }"
should be taken as an idiom and should not be subject to s/0/NULL/
conversion.

> [Luc, this topic came up on the sparse and kernel mailing-lists at one
> point, but I didn't get around to posting my patch to the list - something
> came up. Hopefully, I will find some time to find it and post it soon.]


[References]

*1*

https://lore.kernel.org/git/e6796c60-a870-e761-3b07-b680f934c537@ramsayjones.plus.com/