From: kernel test robot <lkp@intel.com>
To: Martin Liu <liumartin@google.com>,
robh+dt@kernel.org, frowand.list@gmail.com
Cc: oe-kbuild-all@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, surenb@google.com,
minchan@kernel.org, tkjos@google.com, liumartin@google.com
Subject: Re: [PATCH] of: reserved-mem: expose reserved-mem details via debugfs
Date: Tue, 7 Feb 2023 03:57:31 +0800 [thread overview]
Message-ID: <202302070307.dJ4f1zXY-lkp@intel.com> (raw)
In-Reply-To: <20230206142714.4151047-1-liumartin@google.com>
Hi Martin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.2-rc7 next-20230206]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Martin-Liu/of-reserved-mem-expose-reserved-mem-details-via-debugfs/20230206-222927
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20230206142714.4151047-1-liumartin%40google.com
patch subject: [PATCH] of: reserved-mem: expose reserved-mem details via debugfs
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20230207/202302070307.dJ4f1zXY-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/5d479d32b3863f2ec8d10d756aa57cf29046e334
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Martin-Liu/of-reserved-mem-expose-reserved-mem-details-via-debugfs/20230206-222927
git checkout 5d479d32b3863f2ec8d10d756aa57cf29046e334
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k SHELL=/bin/bash drivers/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/of/of_reserved_mem.c: In function 'of_reserved_mem_debug_show':
>> drivers/of/of_reserved_mem.c:465:46: warning: format '%lu' expects argument of type 'long unsigned int', but argument 5 has type 'phys_addr_t' {aka 'unsigned int'} [-Wformat=]
465 | seq_printf(m, "%pa..%pa ( %7lu KB ) %5s %12s %s\n", &rmem->base,
| ~~~^
| |
| long unsigned int
| %7u
466 | &end, rmem->size / 1024,
| ~~~~~~~~~~~~~~~~~
| |
| phys_addr_t {aka unsigned int}
vim +465 drivers/of/of_reserved_mem.c
450
451 #if defined(CONFIG_DEBUG_FS)
452 static int of_reserved_mem_debug_show(struct seq_file *m, void *private)
453 {
454 unsigned int i;
455 size_t sum = 0;
456
457 for (i = 0; i < reserved_mem_count; i++) {
458 const struct reserved_mem *rmem = &reserved_mem[i];
459 unsigned long node = rmem->fdt_node;
460 phys_addr_t end = rmem->base + rmem->size - 1;
461 bool nomap = (of_get_flat_dt_prop(node, "no-map", NULL)) != NULL;
462 bool reusable = (of_get_flat_dt_prop(node, "reusable", NULL)) != NULL;
463
464 sum += rmem->size;
> 465 seq_printf(m, "%pa..%pa ( %7lu KB ) %5s %12s %s\n", &rmem->base,
466 &end, rmem->size / 1024,
467 nomap ? "nomap" : "map",
468 reusable ? "reusable" : "non-reusable",
469 rmem->name ? rmem->name : "unknown");
470 }
471 seq_printf(m, "Total %d regions, %zu KB\n",
472 reserved_mem_count,
473 sum / 1024);
474 return 0;
475 }
476 DEFINE_SHOW_ATTRIBUTE(of_reserved_mem_debug);
477
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-02-06 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:27 Martin Liu
2023-02-06 15:12 ` Rob Herring
2023-02-07 17:05 ` Martin Liu
2023-02-07 21:04 ` Rob Herring
2023-02-08 8:59 ` Martin Liu
2023-02-06 17:24 ` kernel test robot
2023-02-06 19:57 ` kernel test robot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202302070307.dJ4f1zXY-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liumartin@google.com \
--cc=minchan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=surenb@google.com \
--cc=tkjos@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®