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, willy@infradead.org,
	akpm@linux-foundation.org, mhocko@suse.com,
	kirill.shutemov@linux.intel.com, dan.j.williams@intel.com,
	vbabka@suse.cz, riel@redhat.com, rppt@linux.ibm.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: Create the new vm_fault_t type
Date: Tue, 6 Nov 2018 21:27:13 +0800	[thread overview]
Message-ID: <201811062135.m1acUE2w%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181106074934.GA27620@jordon-HP-15-Notebook-PC>

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

Hi Souptick,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v4.20-rc1 next-20181106]
[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-Create-the-new-vm_fault_t-type/20181106-171908
config: i386-randconfig-h1-11061829 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

>> drivers//dma-buf/udmabuf.c:34:2: warning: initialization from incompatible pointer type
     .fault = udmabuf_vm_fault,
     ^
   drivers//dma-buf/udmabuf.c:34:2: warning: (near initialization for 'udmabuf_vm_ops.fault')

vim +34 drivers//dma-buf/udmabuf.c

fbb0de79 Gerd Hoffmann 2018-08-27  32  
fbb0de79 Gerd Hoffmann 2018-08-27  33  static const struct vm_operations_struct udmabuf_vm_ops = {
fbb0de79 Gerd Hoffmann 2018-08-27 @34  	.fault = udmabuf_vm_fault,
fbb0de79 Gerd Hoffmann 2018-08-27  35  };
fbb0de79 Gerd Hoffmann 2018-08-27  36  

:::::: The code at line 34 was first introduced by commit
:::::: fbb0de795078190a9834b3409e4b009cfb18a6d4 Add udmabuf misc device

:::::: TO: Gerd Hoffmann <kraxel@redhat.com>
:::::: CC: Gerd Hoffmann <kraxel@redhat.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: 31349 bytes --]

      parent reply	other threads:[~2018-11-06 13:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  7:49 Souptick Joarder
2018-11-06  8:26 ` Mike Rapoport
2018-11-06  8:34   ` Souptick Joarder
2018-11-06  9:00     ` Mike Rapoport
2018-11-06 13:27 ` kbuild 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=201811062135.m1acUE2w%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jrdr.linux@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=riel@redhat.com \
    --cc=rppt@linux.ibm.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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