From: kbuild test robot <lkp@intel.com>
To: Insu Yun <wuninsu@gmail.com>
Cc: kbuild-all@01.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
taesoo@gatech.edu, yeongjin.jang@gatech.edu, insu@gatech.edu,
changwoo@gatech.edu, Insu Yun <wuninsu@gmail.com>
Subject: Re: [PATCH] qxl: correctly handling failed allocation
Date: Wed, 30 Dec 2015 03:26:43 +0800 [thread overview]
Message-ID: <201512300315.a7vBYpGa%fengguang.wu@intel.com> (raw)
In-Reply-To: <1451416674-10618-1-git-send-email-wuninsu@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
Hi Insu,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.4-rc7 next-20151223]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Insu-Yun/qxl-correctly-handling-failed-allocation/20151230-031647
base: git://people.freedesktop.org/~airlied/linux.git drm-next
config: x86_64-randconfig-x008-12291635 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/gpu/drm/qxl/qxl_kms.c: In function 'qxl_device_init':
>> drivers/gpu/drm/qxl/qxl_kms.c:224:11: error: 'struct qxl_device' has no member named 'memslots'
if (!qdev->memslots)
^
vim +224 drivers/gpu/drm/qxl/qxl_kms.c
218 (~(uint64_t)0) >> (qdev->slot_id_bits + qdev->slot_gen_bits);
219
220 qdev->mem_slots =
221 kmalloc(qdev->n_mem_slots * sizeof(struct qxl_memslot),
222 GFP_KERNEL);
223
> 224 if (!qdev->memslots)
225 return -ENOMEM;
226
227 idr_init(&qdev->release_idr);
---
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: 32837 bytes --]
next prev parent reply other threads:[~2015-12-29 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 19:17 Insu Yun
2015-12-29 19:26 ` kbuild test robot [this message]
2015-12-29 19:26 ` kbuild test robot
2016-07-09 13:41 ` 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=201512300315.a7vBYpGa%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=changwoo@gatech.edu \
--cc=dri-devel@lists.freedesktop.org \
--cc=insu@gatech.edu \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taesoo@gatech.edu \
--cc=wuninsu@gmail.com \
--cc=yeongjin.jang@gatech.edu \
/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®