From: kbuild test robot <lkp@intel.com>
To: Tommy Nguyen <remyabel@gmail.com>
Cc: kbuild-all@01.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
linux-kernel@vger.kernel.org, "Tommy Nguyen" <remyabel@gmail.com>
Subject: Re: [PATCH] staging: android: ion: Use DEFINE_DEBUGFS_ATTRIBUTE
Date: Wed, 28 Jun 2017 01:44:17 +0800 [thread overview]
Message-ID: <201706280109.eAPBpqVr%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170625122206.4229-1-remyabel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
Hi Tommy,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.12-rc7 next-20170627]
[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/Tommy-Nguyen/staging-android-ion-Use-DEFINE_DEBUGFS_ATTRIBUTE/20170626-055654
config: x86_64-randconfig-s3-06280039 (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/staging/android/ion/ion.c: In function 'ion_device_add_heap':
>> drivers/staging/android/ion/ion.c:572:16: error: implicit declaration of function 'debugfs_create_file_unsafe' [-Werror=implicit-function-declaration]
debug_file = debugfs_create_file_unsafe(
^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/staging/android/ion/ion.c:572:14: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
debug_file = debugfs_create_file_unsafe(
^
cc1: some warnings being treated as errors
vim +/debugfs_create_file_unsafe +572 drivers/staging/android/ion/ion.c
566 plist_add(&heap->node, &dev->heaps);
567
568 if (heap->shrinker.count_objects && heap->shrinker.scan_objects) {
569 char debug_name[64];
570
571 snprintf(debug_name, 64, "%s_shrink", heap->name);
> 572 debug_file = debugfs_create_file_unsafe(
573 debug_name, 0644, dev->debug_root, heap,
574 &debug_shrink_fops);
575 if (!debug_file) {
---
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: 28062 bytes --]
prev parent reply other threads:[~2017-06-27 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 12:22 Tommy Nguyen
2017-06-25 12:56 ` Greg Kroah-Hartman
2017-06-27 17:44 ` kbuild test robot [this message]
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=201706280109.eAPBpqVr%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arve@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=remyabel@gmail.com \
--cc=riandrews@android.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
all inboxes | Powered by JetHome®