From: Souptick Joarder <jrdr.linux@gmail.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: kbuild test robot <lkp@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kwiboo-linux-rockchip:rockchip-5.1-patches-from-5.3-v5.1.5 83/106] drivers/gpu//drm/rockchip/rockchip_drm_gem.c:230:9: error: implicit declaration of function 'vm_map_pages'; did you mean 'vma_pages'?
Date: Sun, 26 May 2019 21:24:46 +0530 [thread overview]
Message-ID: <CAFqt6zZYkGMGsD2XYdoXunD+fDTRs+3MMAoVVs7s2BWQa=nffw@mail.gmail.com> (raw)
In-Reply-To: <VI1PR03MB4206678FD979F4855AE26BA5AC1C0@VI1PR03MB4206.eurprd03.prod.outlook.com>
On Sun, May 26, 2019 at 9:07 PM Jonas Karlman <jonas@kwiboo.se> wrote:
>
> On 2019-05-26 17:25, Souptick Joarder wrote:
> > Hi Jonas,
> >
> > On Sun, May 26, 2019 at 4:29 PM kbuild test robot <lkp@intel.com> wrote:
> >> tree: https://github.com/Kwiboo/linux-rockchip rockchip-5.1-patches-from-5.3-v5.1.5
> >> head: 622dad206e3b82c53acac1857f8a6ff970c0d01b
> >> commit: 4004964b0854f3258032a723627d487882a74380 [83/106] drm/rockchip/rockchip_drm_gem.c: convert to use vm_map_pages()
> >> config: arm64-allyesconfig (attached as .config)
> >> compiler: aarch64-linux-gcc (GCC) 7.4.0
> >> reproduce:
> >> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> >> chmod +x ~/bin/make.cross
> >> git checkout 4004964b0854f3258032a723627d487882a74380
> >> # save the attached .config to linux build tree
> >> GCC_VERSION=7.4.0 make.cross ARCH=arm64
> >>
> >> If you fix the issue, kindly add following tag
> >> Reported-by: kbuild test robot <lkp@intel.com>
> >>
> >> All errors (new ones prefixed by >>):
> >>
> >> drivers/gpu//drm/rockchip/rockchip_drm_gem.c: In function 'rockchip_drm_gem_object_mmap_iommu':
> >>>> drivers/gpu//drm/rockchip/rockchip_drm_gem.c:230:9: error: implicit declaration of function 'vm_map_pages'; did you mean 'vma_pages'? [-Werror=implicit-function-declaration]
> >> return vm_map_pages(vma, rk_obj->pages, count);
> >> ^~~~~~~~~~~~
> >> vma_pages
> >> cc1: some warnings being treated as errors
> > Looking into https://github.com/Kwiboo/linux-rockchip/blob/rockchip-5.1-patches-from-5.3-v5.1.5/mm/memory.c
> > vm_map_pages() API is missing. vm_map_pages() merged into 5.2-rc1.
> > Is the below match merged into https://github.com/Kwiboo/linux-rockchip ?
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc1&id=a667d7456f189e3422725dddcd067537feac49c0
>
> Thanks for looking, I do not know why kbuild test robot have started building from my github tree,
> I pushed a v5.1 branch with cherry-picked commits from v5.2+next before I did a local build test and kbuild test robot started making some unnecessary noise.
Thanks for your quick response. I think, if kbuild picked your github tree
wrongly, you need to notify kbuild for the same.
> Will be more careful not to push code before making a local test build.
>
> Regards,
> Jonas
>
> >> vim +230 drivers/gpu//drm/rockchip/rockchip_drm_gem.c
> >>
> >> 219
> >> 220 static int rockchip_drm_gem_object_mmap_iommu(struct drm_gem_object *obj,
> >> 221 struct vm_area_struct *vma)
> >> 222 {
> >> 223 struct rockchip_gem_object *rk_obj = to_rockchip_obj(obj);
> >> 224 unsigned int count = obj->size >> PAGE_SHIFT;
> >> 225 unsigned long user_count = vma_pages(vma);
> >> 226
> >> 227 if (user_count == 0)
> >> 228 return -ENXIO;
> >> 229
> >> > 230 return vm_map_pages(vma, rk_obj->pages, count);
> >> 231 }
> >> 232
> >>
> >> ---
> >> 0-DAY kernel test infrastructure Open Source Technology Center
> >> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
prev parent reply other threads:[~2019-05-26 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 10:58 [kwiboo-linux-rockchip:rockchip-5.1-patches-from-5.3-v5.1.5 83/106] drivers/gpu//drm/rockchip/rockchip_drm_gem.c:230:9: error: implicit declaration of function 'vm_map_pages'; did you mean 'vma_pages'? kbuild test robot
2019-05-26 15:25 ` Souptick Joarder
2019-05-26 15:36 ` Jonas Karlman
2019-05-26 15:54 ` Souptick Joarder [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='CAFqt6zZYkGMGsD2XYdoXunD+fDTRs+3MMAoVVs7s2BWQa=nffw@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jonas@kwiboo.se \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).