[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2Cq5oa8e7SAQ-mOGnytEjnOa4esr1gsfsS3ceH+A2f2g@mail.gmail.com>
Date: Mon, 2 May 2022 08:39:12 +0200
From: Arnd Bergmann <arnd@...db.de>
To: kernel test robot <lkp@...el.com>
Cc: Sven Peter <sven@...npeter.dev>,
clang-built-linux <llvm@...ts.linux.dev>,
kbuild-all@...ts.01.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>, Hector Martin <marcan@...can.st>
Subject: Re: [asahilinux:asahi-soc/rtkit-sart-nvme 4/6] drivers/soc/apple/sart.c:284:4:
warning: format specifies type 'unsigned long long' but the argument has type
'phys_addr_t' (aka 'unsigned int')
On Mon, May 2, 2022 at 2:21 AM kernel test robot <lkp@...el.com> wrote:
> 277
> 278 clear_bit(i, &sart->used_entries);
> 279 dev_dbg(sart->dev, "cleared entry %d\n", i);
> 280 return 0;
> 281 }
> 282
> 283 dev_warn(sart->dev, "entry [paddr: 0x%llx, size: 0x%zx] not found\n",
> > 284 paddr, size);
> 285
Hi Sven,
to print a phys_addr_t, you should pass the address by reference and use
the special "%pap" format string modifier. I'm not entirely sure if it should
actually be a dma_addr_t instead of a phys_addr_t. If the type gets changed,
the format string would become "%pad".
Arnd
Powered by blists - more mailing lists