From: kbuild test robot <lkp@intel.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: kbuild-all@01.org,
Patrik Jakobsson <patrik.r.jakobsson@gmail.com>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH] drm/gma500: dont expose bytes from kernel stack
Date: Mon, 22 Aug 2016 21:45:47 +0800 [thread overview]
Message-ID: <201608222109.5We0JG2j%fengguang.wu@intel.com> (raw)
In-Reply-To: <1471804778-3656-1-git-send-email-xypron.glpk@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
Hi Heinrich,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.8-rc3 next-20160822]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Heinrich-Schuchardt/drm-gma500-dont-expose-bytes-from-kernel-stack/20160822-024132
base: git://people.freedesktop.org/~airlied/linux.git drm-next
config: x86_64-randconfig-x015-201634 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/gpu/drm/gma500/oaktrail_crtc.c: In function 'mrst_sdvo_find_best_pll':
>> drivers/gpu/drm/gma500/oaktrail_crtc.c:141:9: error: incompatible type for argument 1 of 'memset'
memset(clock, 0, sizeof(struct gma_clock_t));
^~~~~
In file included from arch/x86/include/asm/string.h:4:0,
from include/linux/string.h:18,
from include/uapi/linux/uuid.h:21,
from include/linux/uuid.h:19,
from include/linux/mod_devicetable.h:12,
from include/linux/i2c.h:29,
from drivers/gpu/drm/gma500/oaktrail_crtc.c:18:
arch/x86/include/asm/string_64.h:55:7: note: expected 'void *' but argument is of type 'struct gma_clock_t'
void *memset(void *s, int c, size_t n);
^~~~~~
vim +/memset +141 drivers/gpu/drm/gma500/oaktrail_crtc.c
135 int refclk, struct gma_clock_t *best_clock)
136 {
137 struct gma_clock_t clock;
138 u32 target_vco, actual_freq;
139 s32 freq_error, min_error = 100000;
140
> 141 memset(clock, 0, sizeof(struct gma_clock_t));
142 memset(best_clock, 0, sizeof(*best_clock));
143
144 for (clock.m = limit->m.min; clock.m <= limit->m.max; clock.m++) {
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 31106 bytes --]
next prev parent reply other threads:[~2016-08-22 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 18:39 Heinrich Schuchardt
2016-08-21 18:46 ` Joe Perches
2016-08-21 19:35 ` Heinrich Schuchardt
2016-08-21 19:38 ` Joe Perches
2016-08-22 7:29 ` Daniel Vetter
2016-08-22 9:16 ` One Thousand Gnomes
2016-08-22 8:32 ` Jani Nikula
2016-08-22 13:45 ` kbuild test robot [this message]
2016-08-22 17:18 ` 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=201608222109.5We0JG2j%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
--cc=xypron.glpk@gmx.de \
/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
all inboxes | Powered by JetHome®