From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
virtualization@lists.linux-foundation.org,
Gerd Hoffmann <kraxel@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel.vetter@intel.com>,
Emil Velikov <emil.velikov@collabora.com>
Subject: Re: [PATCH] drm/simple-kms: Standardize arguments for callbacks
Date: Wed, 23 Oct 2019 13:55:38 +0800 [thread overview]
Message-ID: <201910231343.cn5i5UQp%lkp@intel.com> (raw)
In-Reply-To: <20191022155536.27939-1-daniel.vetter@ffwll.ch>
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc4 next-20191022]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Daniel-Vetter/drm-simple-kms-Standardize-arguments-for-callbacks/20191023-073731
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 3b7c59a1950c75f2c0152e5a9cd77675b09233d6
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-dirty
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/xen/xen_drm_front_kms.c:289:23: sparse: sparse: incorrect type in initializer (incompatible argument 1 (different base types)) @@ expected int enum drm_mode_status ( *mode_valid )( ... ) @@ got int enum drm_mode_status ( *mode_valid )( ... ) @@
>> drivers/gpu/drm/xen/xen_drm_front_kms.c:289:23: sparse: expected int enum drm_mode_status ( *mode_valid )( ... )
>> drivers/gpu/drm/xen/xen_drm_front_kms.c:289:23: sparse: got int enum drm_mode_status ( * )( ... )
vim +289 drivers/gpu/drm/xen/xen_drm_front_kms.c
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 287
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 288 static const struct drm_simple_display_pipe_funcs display_funcs = {
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 @289 .mode_valid = display_mode_valid,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 290 .enable = display_enable,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 291 .disable = display_disable,
dd388ee1ecbb8c Daniel Vetter 2018-04-09 292 .prepare_fb = drm_gem_fb_simple_display_pipe_prepare_fb,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 293 .update = display_update,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 294 };
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 295
:::::: The code at line 289 was first introduced by commit
:::::: c575b7eeb89f94356997abd62d6d5a0590e259b7 drm/xen-front: Add support for Xen PV display frontend
:::::: TO: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
:::::: CC: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
---
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
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] drm/simple-kms: Standardize arguments for callbacks
Date: Wed, 23 Oct 2019 13:55:38 +0800 [thread overview]
Message-ID: <201910231343.cn5i5UQp%lkp@intel.com> (raw)
In-Reply-To: <20191022155536.27939-1-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 2762 bytes --]
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc4 next-20191022]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Daniel-Vetter/drm-simple-kms-Standardize-arguments-for-callbacks/20191023-073731
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 3b7c59a1950c75f2c0152e5a9cd77675b09233d6
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-dirty
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/xen/xen_drm_front_kms.c:289:23: sparse: sparse: incorrect type in initializer (incompatible argument 1 (different base types)) @@ expected int enum drm_mode_status ( *mode_valid )( ... ) @@ got int enum drm_mode_status ( *mode_valid )( ... ) @@
>> drivers/gpu/drm/xen/xen_drm_front_kms.c:289:23: sparse: expected int enum drm_mode_status ( *mode_valid )( ... )
>> drivers/gpu/drm/xen/xen_drm_front_kms.c:289:23: sparse: got int enum drm_mode_status ( * )( ... )
vim +289 drivers/gpu/drm/xen/xen_drm_front_kms.c
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 287
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 288 static const struct drm_simple_display_pipe_funcs display_funcs = {
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 @289 .mode_valid = display_mode_valid,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 290 .enable = display_enable,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 291 .disable = display_disable,
dd388ee1ecbb8c Daniel Vetter 2018-04-09 292 .prepare_fb = drm_gem_fb_simple_display_pipe_prepare_fb,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 293 .update = display_update,
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 294 };
c575b7eeb89f94 Oleksandr Andrushchenko 2018-04-03 295
:::::: The code at line 289 was first introduced by commit
:::::: c575b7eeb89f94356997abd62d6d5a0590e259b7 drm/xen-front: Add support for Xen PV display frontend
:::::: TO: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
:::::: CC: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-10-23 5:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 15:55 [PATCH] drm/simple-kms: Standardize arguments for callbacks Daniel Vetter
2019-10-22 17:16 ` Thomas Zimmermann
2019-10-22 17:16 ` Thomas Zimmermann
2019-10-22 19:03 ` Daniel Vetter
2019-10-23 6:47 ` Thomas Zimmermann
2019-10-23 8:53 ` Daniel Vetter
2019-10-23 8:53 ` Daniel Vetter
2019-10-23 6:47 ` Thomas Zimmermann
2019-10-23 0:43 ` kbuild test robot
2019-10-23 0:43 ` kbuild test robot
2019-10-23 0:43 ` kbuild test robot
2019-10-23 5:55 ` kbuild test robot [this message]
2019-10-23 5:55 ` kbuild test robot
2019-10-23 5:55 ` kbuild test robot
2019-10-22 15:55 Daniel Vetter
2019-10-23 10:12 Daniel Vetter
2019-10-23 10:12 ` Daniel Vetter
2019-10-23 15:40 ` Linus Walleij
2019-10-23 15:40 ` Linus Walleij
2019-10-24 11:55 ` Daniel Vetter
2019-10-24 11:55 ` Daniel Vetter
2019-10-24 11:55 ` 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=201910231343.cn5i5UQp%lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.velikov@collabora.com \
--cc=kbuild-all@lists.01.org \
--cc=kraxel@redhat.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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 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.