From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, seanpaul@chromium.org,
jbaron@akamai.com
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
Jim Cromie <jim.cromie@gmail.com>
Subject: Re: [Intel-gfx] [PATCH] dyndbg: add special aux_print framework
Date: Sun, 1 Aug 2021 14:01:08 +0800 [thread overview]
Message-ID: <202108011346.XRFIWo3r-lkp@intel.com> (raw)
In-Reply-To: <20210801033548.832022-1-jim.cromie@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3146 bytes --]
Hi Jim,
I love your patch! Yet something to improve:
[auto build test ERROR on tegra-drm/drm/tegra/for-next]
[also build test ERROR on linux/master linus/master v5.14-rc3 next-20210730]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Jim-Cromie/dyndbg-add-special-aux_print-framework/20210801-113749
base: git://anongit.freedesktop.org/tegra/linux.git drm/tegra/for-next
config: x86_64-randconfig-a012-20210801 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 4f71f59bf3d9914188a11d0c41bedbb339d36ff5)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/1bf22862d95adc83487ade34fe1c42707f94ac4d
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jim-Cromie/dyndbg-add-special-aux_print-framework/20210801-113749
git checkout 1bf22862d95adc83487ade34fe1c42707f94ac4d
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=x86_64 SHELL=/bin/bash
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 >>):
>> lib/dynamic_debug.c:651:19: error: no member named 'aux_channel' in 'struct _ddebug'
if (descriptor->aux_channel) {
~~~~~~~~~~ ^
lib/dynamic_debug.c:653:18: error: no member named 'aux_channel' in 'struct _ddebug'
(*descriptor->aux_channel)
~~~~~~~~~~ ^
2 errors generated.
vim +651 lib/dynamic_debug.c
626
627 void __dynamic_pr_debug(struct _ddebug *descriptor, const char *fmt, ...)
628 {
629 va_list args;
630 struct va_format vaf;
631 char buf[PREFIX_SIZE] = "";
632
633 BUG_ON(!descriptor);
634 BUG_ON(!fmt);
635
636 va_start(args, fmt);
637
638 vaf.fmt = fmt;
639 vaf.va = &args;
640
641 printk(KERN_DEBUG "%s%pV", dynamic_emit_prefix(descriptor, buf), &vaf);
642
643 if (descriptor->flags & _DPRINTK_FLAGS_PRINT_AUX) {
644 /* our model:
645 drm_trace_printf("%s%s[" DRM_NAME ":%ps] %pV",
646 dev ? dev_name(dev) : "", dev ? " " : "",
647 __builtin_return_address(0), &vaf);
648 */
649 pr_info("reached check aux\n");
650
> 651 if (descriptor->aux_channel) {
652 pr_info("calling aux\n");
653 (*descriptor->aux_channel)
654 ("%s[DRM_mumble :%ps] %pV", buf,
655 __builtin_return_address(0), &vaf);
656 }
657 }
658 va_end(args);
659 }
660 EXPORT_SYMBOL(__dynamic_pr_debug);
661
---
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: 37541 bytes --]
next prev parent reply other threads:[~2021-08-01 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 3:35 [Intel-gfx] [PATCH] dyndbg: add special aux_print framework Jim Cromie
2021-08-01 3:42 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for dyndbg: add special aux_print framework (rev2) Patchwork
2021-08-01 5:48 ` [Intel-gfx] [PATCH] dyndbg: add special aux_print framework kernel test robot
2021-08-01 6:01 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-01 3:34 Jim Cromie
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=202108011346.XRFIWo3r-lkp@intel.com \
--to=lkp@intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.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 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).