From: kbuild test robot <lkp@intel.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: kbuild-all@01.org, mawilcox@microsoft.com,
ross.zwisler@linux.intel.com, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: dax: Adding new return type vm_fault_t
Date: Wed, 18 Apr 2018 17:18:32 +0800 [thread overview]
Message-ID: <201804181542.1UXBIRLs%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180417153507.GA31905@jordon-HP-15-Notebook-PC>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Hi Souptick,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16]
[cannot apply to linus/master v4.17-rc1 next-20180418]
[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/fs-dax-Adding-new-return-type-vm_fault_t/20180418-152151
config: i386-randconfig-x014-201815 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/mempolicy.h:11:0,
from include/linux/migrate.h:6,
from fs//btrfs/disk-io.c:29:
>> include/linux/dax.h:100:1: error: unknown type name 'vm_fault_t'; did you mean 'vm_flags_t'?
vm_fault_t dax_finish_sync_fault(struct vm_fault *vmf,
^~~~~~~~~~
vm_flags_t
vim +100 include/linux/dax.h
95
96 ssize_t dax_iomap_rw(struct kiocb *iocb, struct iov_iter *iter,
97 const struct iomap_ops *ops);
98 int dax_iomap_fault(struct vm_fault *vmf, enum page_entry_size pe_size,
99 pfn_t *pfnp, int *errp, const struct iomap_ops *ops);
> 100 vm_fault_t dax_finish_sync_fault(struct vm_fault *vmf,
101 enum page_entry_size pe_size, pfn_t pfn);
102 int dax_delete_mapping_entry(struct address_space *mapping, pgoff_t index);
103 int dax_invalidate_mapping_entry_sync(struct address_space *mapping,
104 pgoff_t index);
105
---
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: 29322 bytes --]
next prev parent reply other threads:[~2018-04-18 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:35 [PATCH] fs: dax: Adding new return type vm_fault_t Souptick Joarder
2018-04-17 20:26 ` Ross Zwisler
2018-04-17 21:00 ` Matthew Wilcox
2018-04-20 19:21 ` Souptick Joarder
2018-04-20 20:47 ` Matthew Wilcox
2018-04-21 17:26 ` Souptick Joarder
2018-04-18 9:02 ` kbuild test robot
2018-04-18 9:18 ` kbuild test robot [this message]
2018-04-18 11:38 ` Souptick Joarder
2018-04-18 12:13 ` Fengguang Wu
2018-04-18 15:41 ` Ross Zwisler
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=201804181542.1UXBIRLs%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jrdr.linux@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.