From: kbuild test robot <lkp@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] dma-buf/sync-file: Defer creation of sync_file->name
Date: Tue, 16 May 2017 18:21:52 +0800 [thread overview]
Message-ID: <201705161823.kwIiB5pt%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170512113042.14646-1-chris@chris-wilson.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
Hi Chris,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc1 next-20170516]
[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/Chris-Wilson/dma-buf-sync-file-Defer-creation-of-sync_file-name/20170512-193751
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers//dma-buf/sync_debug.c: In function 'sync_print_sync_file':
>> drivers//dma-buf/sync_debug.c:137:53: error: 'struct sync_file' has no member named 'name'
seq_printf(s, "[%p] %s: %s\n", sync_file, sync_file->name,
^~
vim +137 drivers//dma-buf/sync_debug.c
0f0d8406 drivers/staging/android/sync_debug.c Maarten Lankhorst 2014-07-01 131
d7fdb0ae drivers/staging/android/sync_debug.c Gustavo Padovan 2016-01-21 132 static void sync_print_sync_file(struct seq_file *s,
d7fdb0ae drivers/staging/android/sync_debug.c Gustavo Padovan 2016-01-21 133 struct sync_file *sync_file)
0f0d8406 drivers/staging/android/sync_debug.c Maarten Lankhorst 2014-07-01 134 {
0f0d8406 drivers/staging/android/sync_debug.c Maarten Lankhorst 2014-07-01 135 int i;
0f0d8406 drivers/staging/android/sync_debug.c Maarten Lankhorst 2014-07-01 136
d7fdb0ae drivers/staging/android/sync_debug.c Gustavo Padovan 2016-01-21 @137 seq_printf(s, "[%p] %s: %s\n", sync_file, sync_file->name,
d6c99f4b drivers/dma-buf/sync_debug.c Chris Wilson 2017-01-04 138 sync_status_str(dma_fence_get_status(sync_file->fence)));
0f0d8406 drivers/staging/android/sync_debug.c Maarten Lankhorst 2014-07-01 139
f54d1867 drivers/dma-buf/sync_debug.c Chris Wilson 2016-10-25 140 if (dma_fence_is_array(sync_file->fence)) {
:::::: The code at line 137 was first introduced by commit
:::::: d7fdb0ae9d115fa14ff3a5382c8a62de41c7786a staging/android: rename sync_fence to sync_file
:::::: TO: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39258 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-16 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 11:30 [PATCH] dma-buf/sync-file: Defer creation of sync_file->name Chris Wilson
2017-05-12 12:48 ` kbuild test robot
2017-05-12 14:39 ` Gustavo Padovan
2017-05-12 18:55 ` [PATCH v3] " Chris Wilson
2017-05-15 7:01 ` Daniel Vetter
2017-05-15 8:53 ` [Intel-gfx] " Chris Wilson
2017-05-15 10:10 ` [PATCH v4] " Chris Wilson
2017-05-15 10:50 ` David Herrmann
2017-05-15 11:42 ` Chris Wilson
2017-05-15 11:51 ` David Herrmann
2017-05-16 11:10 ` [PATCH v5] " Chris Wilson
2017-05-22 9:21 ` Chris Wilson
2017-05-22 19:31 ` Daniel Vetter
2017-05-25 1:38 ` Gustavo Padovan
2017-05-12 19:22 ` ✓ Fi.CI.BAT: success for dma-buf/sync-file: Defer creation of sync_file->name (rev2) Patchwork
2017-05-15 11:28 ` ✓ Fi.CI.BAT: success for dma-buf/sync-file: Defer creation of sync_file->name (rev3) Patchwork
2017-05-16 10:21 ` kbuild test robot [this message]
2017-05-16 12:05 ` ✓ Fi.CI.BAT: success for dma-buf/sync-file: Defer creation of sync_file->name (rev4) Patchwork
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=201705161823.kwIiB5pt%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.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.