Re: txtimestamp.c:164:29: warning: format '0' expects argument of type 'long unsigned int', but argument 3 has type 'int64_t' {aka 'long long int'} [-Wformat=]

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Thu, Jan 06, 2022 at 03:39:09PM +0530, Naresh Kamboju wrote:
> While building selftests the following warnings were noticed for arm
> architecture on Linux stable v5.15.13 kernel and also on Linus's tree.
> 
> arm-linux-gnueabihf-gcc -Wall -Wl,--no-as-needed -O2 -g
> -I../../../../usr/include/    txtimestamp.c  -o
> /home/tuxbuild/.cache/tuxmake/builds/current/kselftest/net/txtimestamp
> txtimestamp.c: In function 'validate_timestamp':
> txtimestamp.c:164:29: warning: format '0' expects argument of type
> 'long unsigned int', but argument 3 has type 'int64_t' {aka 'long long
> int'} [-Wformat=]
>   164 |   fprintf(stderr, "ERROR: 0 us expected between 0 and 0\n",
>       |                           ~~^
>       |                             |
>       |                             long unsigned int
>       |                           0
>   165 |     cur64 - start64, min_delay, max_delay);
>       |     ~~~~~~~~~~~~~~~
>       |           |
>       |           int64_t {aka long long int}
> txtimestamp.c: In function '__print_ts_delta_formatted':
> txtimestamp.c:173:22: warning: format '0' expects argument of type
> 'long unsigned int', but argument 3 has type 'int64_t' {aka 'long long
> int'} [-Wformat=]
>   173 |   fprintf(stderr, "0 ns", ts_delta);
>       |                    ~~^      ~~~~~~~~
>       |                      |      |
>       |                      |      int64_t {aka long long int}
>       |                      long unsigned int
>       |                    0
> txtimestamp.c:175:22: warning: format '0' expects argument of type
> 'long unsigned int', but argument 3 has type 'int64_t' {aka 'long long
> int'} [-Wformat=]
>   175 |   fprintf(stderr, "0 us", ts_delta / NSEC_PER_USEC);
>       |                    ~~^
>       |                      |
>       |                      long unsigned int
>       |                    0
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> build link:
> https://builds.tuxbuild.com/23HFntxpqyCx0RbiuadfGZ36Kym/
> 
> metadata:
>   git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>   git commit: 734eb1fd2073f503f5c6b44f1c0d453ca6986b84
>   git describe: v5.15.13
>   toolchain: gcc-11
>   kernel-config: https://builds.tuxbuild.com/23HFntxpqyCx0RbiuadfGZ36Kym/config
> 
> 
> # To install tuxmake on your system globally:
> # sudo pip3 install -U tuxmake
> 
> tuxmake --runtime podman --target-arch arm --toolchain gcc-10 \
>  --kconfig https://builds.tuxbuild.com/23HFntxpqyCx0RbiuadfGZ36Kym/config \
>   dtbs dtbs-legacy headers kernel kselftest kselftest-merge modules

Same question as before, is this a regression, and if so, any pointers
to a fix?

thanks,

greg k-h