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 05:38:16PM +0530, Naresh Kamboju wrote:
> On Thu, 6 Jan 2022 at 16:07, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > 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",
> 
> <trim>
> 
> > Same question as before, is this a regression, and if so, any pointers
> > to a fix?
> 
> This is a known warning on Linus's tree.

Great, please report the issue there, as there's nothing I can do about
it in the 5.15.y tree until it is resolved there as you know.

thanks,

greg k-h