linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
	willy@infradead.org, mhocko@suse.com, boris.ostrovsky@oracle.com,
	jgross@suse.com, linux@armlinux.org.uk, robin.murphy@arm.com,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v3 8/9] xen/gntdev.c: Convert to use vm_map_pages()
Date: Thu, 14 Feb 2019 23:59:32 +0800	[thread overview]
Message-ID: <201902142325.36JLmKBx%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190213140728.GA22080@jordon-HP-15-Notebook-PC>

[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

Hi Souptick,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc4 next-20190214]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Souptick-Joarder/mm-Use-vm_map_pages-and-vm_map_pages_zero-API/20190214-213457
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-8 (Debian 8.2.0-20) 8.2.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   drivers/xen/gntdev.c: In function 'gntdev_mmap':
>> drivers/xen/gntdev.c:23:21: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=]
    #define pr_fmt(fmt) "xen:" KBUILD_MODNAME ": " fmt
                        ^~~~~~
   include/linux/dynamic_debug.h:127:35: note: in expansion of macro 'pr_fmt'
      __dynamic_pr_debug(&descriptor, pr_fmt(fmt), \
                                      ^~~~~~
   include/linux/printk.h:335:2: note: in expansion of macro 'dynamic_pr_debug'
     dynamic_pr_debug(fmt, ##__VA_ARGS__)
     ^~~~~~~~~~~~~~~~
   drivers/xen/gntdev.c:1091:2: note: in expansion of macro 'pr_debug'
     pr_debug("map %d+%d at %lx (pgoff %lx)\n",
     ^~~~~~~~

vim +23 drivers/xen/gntdev.c

ab31523c Gerd Hoffmann 2010-12-14  22  
283c0972 Joe Perches   2013-06-28 @23  #define pr_fmt(fmt) "xen:" KBUILD_MODNAME ": " fmt
283c0972 Joe Perches   2013-06-28  24  

:::::: The code at line 23 was first introduced by commit
:::::: 283c0972d53769ee44750cad4c27e3f5fa26ec1f xen: Convert printks to pr_<level>

:::::: TO: Joe Perches <joe@perches.com>
:::::: CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66528 bytes --]

  reply	other threads:[~2019-02-14 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 14:07 Souptick Joarder
2019-02-14 15:59 ` kbuild test robot [this message]
2019-02-14 16:55 ` kbuild test robot

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=201902142325.36JLmKBx%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=jrdr.linux@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@armlinux.org.uk \
    --cc=mhocko@suse.com \
    --cc=robin.murphy@arm.com \
    --cc=willy@infradead.org \
    --cc=xen-devel@lists.xenproject.org \
    /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