From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Manfred Spraul <manfred@colorfullife.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: [mmotm:master 351/375] drivers/gpu/drm/virtio/virtgpu_prime.c:43:23: sparse: sparse: symbol 'virtgpu_gem_prime_import_sg_table' was not declared. Should it be static?
Date: Fri, 26 Apr 2019 18:27:46 +0800 [thread overview]
Message-ID: <201904261833.Kd9aE58N%lkp@intel.com> (raw)
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 244c9142b31406e378f2cf5999774ffcbb919753
commit: 4a323f14cbb77c852f8420baababbe20304d8ce4 [351/375] linux-next-git-rejects
reproduce:
# apt-get install sparse
git checkout 4a323f14cbb77c852f8420baababbe20304d8ce4
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/virtio/virtgpu_prime.c:43:23: sparse: sparse: symbol 'virtgpu_gem_prime_import_sg_table' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-04-26 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 10:27 kbuild test robot [this message]
2019-04-26 10:27 ` [RFC PATCH mmotm] virtgpu_gem_prime_import_sg_table() can be static 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=201904261833.Kd9aE58N%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.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