From: kbuild test robot <lkp@intel.com>
To: Haneen Mohammed <hamohammed.sa@gmail.com>
Cc: rodrigosiqueiramelo@gmail.com, daniel.vetter@ffwll.ch,
kbuild-all@01.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/vkms: Introduce basic VKMS driver
Date: Tue, 15 May 2018 19:30:52 +0800 [thread overview]
Message-ID: <201805151957.goDXMjfM%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180514143346.GA21695@haneen-vb>
Hi Haneen,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.17-rc5 next-20180514]
[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/Haneen-Mohammed/drm-vkms-Introduce-basic-VKMS-driver/20180515-165648
base: git://people.freedesktop.org/~airlied/linux.git drm-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vkms/vkms_drv.c:43:19: sparse: symbol 'vkms_driver' 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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-15 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:33 [PATCH] drm/vkms: Introduce basic VKMS driver Haneen Mohammed
2018-05-15 11:30 ` [RFC PATCH] drm/vkms: vkms_driver can be static kbuild test robot
2018-05-15 15:39 ` Haneen Mohammed
2018-05-15 17:31 ` Daniel Vetter
2018-05-15 23:43 ` [kbuild-all] " Li, Philip
2018-05-15 11:30 ` kbuild test robot [this message]
2018-05-15 11:32 ` [PATCH] drm/vkms: Introduce basic VKMS driver Daniel Vetter
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=201805151957.goDXMjfM%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=kbuild-all@01.org \
--cc=rodrigosiqueiramelo@gmail.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