public inbox for [email protected]
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <[email protected]>
To: kernel test robot <[email protected]>
Cc: "Sudarshan Rajagopalan" <[email protected]>,
	[email protected],
	"GNU/Weeb Mailing List" <[email protected]>,
	LKML <[email protected]>,
	"Arve Hjønnevåg" <[email protected]>
Subject: Re: [ammarfaizi2-block:google/android/kernel/common/android12-trusty-5.10 1060/5872] arch/arm64/mm/mmu.c:1499:5: warning: no previous prototype for 'check_range_driver_managed'
Date: Thu, 31 Mar 2022 12:12:42 -0700	[thread overview]
Message-ID: <CAJuCfpEObhCKuJeHNqxna1=N1+f738dTDnUjGPFST1PqqAqcVQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Thu, Mar 31, 2022 at 3:17 AM kernel test robot <[email protected]> wrote:
>
> Hi Sudarshan,
>
> FYI, the error/warning still remains.

The warnings has been fixed in later patch:
https://android-review.googlesource.com/c/kernel/common/+/1668705
android12-trusty-5.10 needs to rebase to the latest android12-5.10 to fix this.

>
> tree:   https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android12-trusty-5.10
> head:   07055bfd3d810d41a38354693dfaa55a6f8c0025
> commit: 1b4aca7d82ae9b40145484fa09ceab38a6a06062 [1060/5872] ANDROID: arm64/mm: implement {populate/depopulate}_range_driver_managed
> config: arm64-buildonly-randconfig-r005-20220331 (https://download.01.org/0day-ci/archive/20220331/[email protected]/config)
> compiler: aarch64-linux-gcc (GCC) 11.2.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/ammarfaizi2/linux-block/commit/1b4aca7d82ae9b40145484fa09ceab38a6a06062
>         git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
>         git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android12-trusty-5.10
>         git checkout 1b4aca7d82ae9b40145484fa09ceab38a6a06062
>         # save the config file to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/mm/ drivers/gpu/drm/hisilicon/kirin/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <[email protected]>
>
> All warnings (new ones prefixed by >>):
>
> >> arch/arm64/mm/mmu.c:1499:5: warning: no previous prototype for 'check_range_driver_managed' [-Wmissing-prototypes]
>     1499 | int check_range_driver_managed(u64 start, u64 size, const char *resource_name)
>          |     ^~~~~~~~~~~~~~~~~~~~~~~~~~
>    In file included from include/linux/printk.h:7,
>                     from include/linux/kernel.h:16,
>                     from arch/arm64/mm/mmu.c:11:
>    arch/arm64/mm/mmu.c: In function 'check_range_driver_managed':
>    include/linux/kern_levels.h:5:25: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'u64' {aka 'long long unsigned int'} [-Wformat=]
>        5 | #define KERN_SOH        "\001"          /* ASCII Start Of Header */
>          |                         ^~~~~~
>    include/linux/kern_levels.h:11:25: note: in expansion of macro 'KERN_SOH'
>       11 | #define KERN_ERR        KERN_SOH "3"    /* error conditions */
>          |                         ^~~~~~~~
>    include/linux/printk.h:343:16: note: in expansion of macro 'KERN_ERR'
>      343 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
>          |                ^~~~~~~~
>    arch/arm64/mm/mmu.c:1509:17: note: in expansion of macro 'pr_err'
>     1509 |                 pr_err("%s: couldn't find memory resource for start 0x%lx\n",
>          |                 ^~~~~~
>
>
> vim +/check_range_driver_managed +1499 arch/arm64/mm/mmu.c
>
>   1498
> > 1499  int check_range_driver_managed(u64 start, u64 size, const char *resource_name)
>   1500  {
>   1501          struct mem_section *ms;
>   1502          unsigned long pfn = __phys_to_pfn(start);
>   1503          unsigned long end_pfn = __phys_to_pfn(start + size);
>   1504          struct resource *res;
>   1505          unsigned long flags;
>   1506
>   1507          res = lookup_resource(&iomem_resource, start);
>   1508          if (!res) {
>   1509                  pr_err("%s: couldn't find memory resource for start 0x%lx\n",
>   1510                             __func__, start);
>   1511                  return -EINVAL;
>   1512          }
>   1513
>   1514          flags = res->flags;
>   1515
>   1516          if (!(flags & IORESOURCE_SYSRAM_DRIVER_MANAGED) ||
>   1517              strstr(resource_name, "System RAM (") != resource_name)
>   1518                  return -EINVAL;
>   1519
>   1520          for (; pfn < end_pfn; pfn += PAGES_PER_SECTION) {
>   1521                  ms = __pfn_to_section(pfn);
>   1522                  if (early_section(ms))
>   1523                          return -EINVAL;
>   1524          }
>   1525
>   1526          return 0;
>   1527  }
>   1528
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp

  reply	other threads:[~2022-03-31 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 10:16 [ammarfaizi2-block:google/android/kernel/common/android12-trusty-5.10 1060/5872] arch/arm64/mm/mmu.c:1499:5: warning: no previous prototype for 'check_range_driver_managed' kernel test robot
2022-03-31 19:12 ` Suren Baghdasaryan [this message]
2022-03-31 19:41   ` Arve Hjønnevåg

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='CAJuCfpEObhCKuJeHNqxna1=N1+f738dTDnUjGPFST1PqqAqcVQ@mail.gmail.com' \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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