From: Junio C Hamano <gitster@pobox.com>
Date: Sun, 24 May 2020 16:17:29 GMT
Subject: Re: [PATCH v2] sparse: allow '{ 0 }' to be used without warnings
Message-ID: <xmqqa71xqpd2.fsf@gitster.c.googlers.com>
In-Reply-To: <20200522002502.9010-1-luc.vanoostenryck@gmail.com>

Luc Van Oostenryck <luc.vanoostenryck@gmail.com> writes:

> Note: The option have just been added to Sparse. So, to benefit
>       now from this patch it's needed to use the latest Sparse
>       source from kernel.org. The option will simply be ignored
>       by older versions of Sparse.

The last sentence in this paragraph is very very much appreciated
;-)

>
> [1] https://lore.kernel.org/r/e6796c60-a870-e761-3b07-b680f934c537@ramsayjones.plus.com
> [2] https://lore.kernel.org/r/xmqqd07xem9l.fsf@gitster.c.googlers.com
>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
>
> Change since v1:
> * adapt the commit message to:
>   - fix a typo
>   - give a reference to the Spatch patch
>   - add a note telling the latest Sparse source is needed to
>     benefit from the patch but older versions won't complain.
>
>  Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 3d3a39fc19..69f065ef8c 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1189,7 +1189,7 @@ PTHREAD_CFLAGS =
>  
>  # For the 'sparse' target
>  SPARSE_FLAGS ?=
> -SP_EXTRA_FLAGS =
> +SP_EXTRA_FLAGS = -Wno-universal-initializer
>  
>  # For the 'coccicheck' target; setting SPATCH_BATCH_SIZE higher will
>  # usually result in less CPU usage at the cost of higher peak memory.