From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
"Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-fix-9e 55/55] drivers/gpu/drm/drm_print.c:193:28: error: 'prefix_pad' undeclared
Date: Tue, 23 Jul 2024 10:56:49 +0800 [thread overview]
Message-ID: <202407231007.ds6y11YY-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dd-fix-9e
head: 7e183df2c7882601296e132ddf3598e306961545
commit: 7e183df2c7882601296e132ddf3598e306961545 [55/55] fixup-mismerge-drm-print
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240723/202407231007.ds6y11YY-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240723/202407231007.ds6y11YY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407231007.ds6y11YY-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/device.h:15,
from include/drm/drm_print.h:31,
from drivers/gpu/drm/drm_print.c:36:
drivers/gpu/drm/drm_print.c: In function '__drm_printfn_dbg':
>> drivers/gpu/drm/drm_print.c:193:28: error: 'prefix_pad' undeclared (first use in this function)
193 | prefix_pad, prefix, vaf);
| ^~~~~~~~~~
include/linux/dev_printk.h:129:48: note: in definition of macro 'dev_printk'
129 | _dev_printk(level, dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
drivers/gpu/drm/drm_print.c:193:28: note: each undeclared identifier is reported only once for each function it appears in
193 | prefix_pad, prefix, vaf);
| ^~~~~~~~~~
include/linux/dev_printk.h:129:48: note: in definition of macro 'dev_printk'
129 | _dev_printk(level, dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
>> drivers/gpu/drm/drm_print.c:193:40: error: 'prefix' undeclared (first use in this function)
193 | prefix_pad, prefix, vaf);
| ^~~~~~
include/linux/dev_printk.h:129:48: note: in definition of macro 'dev_printk'
129 | _dev_printk(level, dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
vim +/prefix_pad +193 drivers/gpu/drm/drm_print.c
d8187177b0b195 Rob Clark 2016-11-05 181
9fd6f61a297e94 Jani Nikula 2024-01-16 182 void __drm_printfn_dbg(struct drm_printer *p, struct va_format *vaf)
9fd6f61a297e94 Jani Nikula 2024-01-16 183 {
9fd6f61a297e94 Jani Nikula 2024-01-16 184 const struct drm_device *drm = p->arg;
9fd6f61a297e94 Jani Nikula 2024-01-16 185 const struct device *dev = drm ? drm->dev : NULL;
9fd6f61a297e94 Jani Nikula 2024-01-16 186
cf251030029594 Jim Cromie 2024-04-21 187 if (!__drm_debug_enabled(p->category))
9fd6f61a297e94 Jani Nikula 2024-01-16 188 return;
9fd6f61a297e94 Jani Nikula 2024-01-16 189
9fd6f61a297e94 Jani Nikula 2024-01-16 190 /* Note: __builtin_return_address(0) is useless here. */
9fd6f61a297e94 Jani Nikula 2024-01-16 191 if (dev)
9fd6f61a297e94 Jani Nikula 2024-01-16 192 dev_printk(KERN_DEBUG, dev, "[" DRM_NAME "]%s%s %pV",
9fd6f61a297e94 Jani Nikula 2024-01-16 @193 prefix_pad, prefix, vaf);
9fd6f61a297e94 Jani Nikula 2024-01-16 194 else
9fd6f61a297e94 Jani Nikula 2024-01-16 195 printk(KERN_DEBUG "[" DRM_NAME "]%s%s %pV",
9fd6f61a297e94 Jani Nikula 2024-01-16 196 prefix_pad, prefix, vaf);
9fd6f61a297e94 Jani Nikula 2024-01-16 197 }
9fd6f61a297e94 Jani Nikula 2024-01-16 198 EXPORT_SYMBOL(__drm_printfn_dbg);
9fd6f61a297e94 Jani Nikula 2024-01-16 199
:::::: The code at line 193 was first introduced by commit
:::::: 9fd6f61a297e944fa045a1cb6cd53916d0fea454 drm/print: add drm_dbg_printer() for drm device specific printer
:::::: TO: Jani Nikula <jani.nikula@intel.com>
:::::: CC: Jani Nikula <jani.nikula@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-23 2:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202407231007.ds6y11YY-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ukaszb@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 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.