From: kernel test robot <lkp@intel.com>
To: cgel.zte@gmail.com, jani.nikula@linux.intel.com
Cc: kbuild-all@lists.01.org, airlied@linux.ie,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
yong yiran <yong.yiran@zte.com.cn>,
rodrigo.vivi@intel.com, Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] drm/i915/request: Remove unused variables
Date: Mon, 22 Nov 2021 14:48:22 +0800 [thread overview]
Message-ID: <202111221434.G6MBLqXy-lkp@intel.com> (raw)
In-Reply-To: <20211121101309.23577-1-yong.yiran@zte.com.cn>
[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20211118]
url: https://github.com/0day-ci/linux/commits/cgel-zte-gmail-com/drm-i915-request-Remove-unused-variables/20211121-181441
base: 5191249f880367a4cd675825cd721a8d78f26a45
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/117f34e1836e312bdea3b7c886d829e30f55a094
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review cgel-zte-gmail-com/drm-i915-request-Remove-unused-variables/20211121-181441
git checkout 117f34e1836e312bdea3b7c886d829e30f55a094
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/i915/i915_request.c:2032:12: error: 'print_sched_attr' defined but not used [-Werror=unused-function]
2032 | static int print_sched_attr(const struct i915_sched_attr *attr,
| ^~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/print_sched_attr +2032 drivers/gpu/drm/i915/i915_request.c
7e2e69ed4678a4 Maarten Lankhorst 2021-10-21 2031
1f0e785a9cc09b Chris Wilson 2020-11-19 @2032 static int print_sched_attr(const struct i915_sched_attr *attr,
1f0e785a9cc09b Chris Wilson 2020-11-19 2033 char *buf, int x, int len)
1f0e785a9cc09b Chris Wilson 2020-11-19 2034 {
1f0e785a9cc09b Chris Wilson 2020-11-19 2035 if (attr->priority == I915_PRIORITY_INVALID)
1f0e785a9cc09b Chris Wilson 2020-11-19 2036 return x;
1f0e785a9cc09b Chris Wilson 2020-11-19 2037
1f0e785a9cc09b Chris Wilson 2020-11-19 2038 x += snprintf(buf + x, len - x,
1f0e785a9cc09b Chris Wilson 2020-11-19 2039 " prio=%d", attr->priority);
1f0e785a9cc09b Chris Wilson 2020-11-19 2040
1f0e785a9cc09b Chris Wilson 2020-11-19 2041 return x;
1f0e785a9cc09b Chris Wilson 2020-11-19 2042 }
1f0e785a9cc09b Chris Wilson 2020-11-19 2043
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67189 bytes --]
next prev parent reply other threads:[~2021-11-22 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 10:13 [PATCH linux-next] drm/i915/request: Remove unused variables cgel.zte
2021-11-21 12:18 ` Christophe JAILLET
2021-11-21 12:18 ` Christophe JAILLET
2021-11-22 9:09 ` Jani Nikula
2021-11-22 6:48 ` kernel test robot [this message]
2021-11-22 7:08 ` kernel 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=202111221434.G6MBLqXy-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=cgel.zte@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=yong.yiran@zte.com.cn \
--cc=zealci@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).