From: kernel test robot <lkp@intel.com>
To: Chintan Patel <chintanlike@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Helge Deller <deller@gmx.de>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [linux-next:master 4572/9290] drivers/staging/fbtft/fbtft-core.c:368:16: error: no member named 'dev' in 'struct fb_info'
Date: Fri, 23 Jan 2026 09:51:00 +0800 [thread overview]
Message-ID: <202601230916.VpgbAIF5-lkp@intel.com> (raw)
Hi Chintan,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: a0c666c25aeefd16f4b088c6549a6fb6b65a8a1d
commit: bc9f9cb85a7d49e8d58ab326cb56616166201940 [4572/9290] staging: fbtft: Make FB_DEVICE dependency optional
config: powerpc64-randconfig-r053-20260123 (https://download.01.org/0day-ci/archive/20260123/202601230916.VpgbAIF5-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260123/202601230916.VpgbAIF5-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/202601230916.VpgbAIF5-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/staging/fbtft/fbtft-core.c:368:16: error: no member named 'dev' in 'struct fb_info'
368 | dev_dbg(info->dev,
| ~~~~ ^
drivers/staging/fbtft/fbtft-core.c:394:16: error: no member named 'dev' in 'struct fb_info'
394 | dev_dbg(info->dev, "%s(blank=%d)\n",
| ~~~~ ^
drivers/staging/fbtft/fbtft-core.c:796:20: error: no member named 'dev' in 'struct fb_info'
796 | dev_info(fb_info->dev,
| ~~~~~~~ ^
3 errors generated.
vim +368 drivers/staging/fbtft/fbtft-core.c
c296d5f9957c03 Thomas Petazzoni 2014-12-31 360
1ba539d53b2de2 Bhanusree Pola 2019-02-25 361 static int fbtft_fb_setcolreg(unsigned int regno, unsigned int red,
1ba539d53b2de2 Bhanusree Pola 2019-02-25 362 unsigned int green, unsigned int blue,
1ba539d53b2de2 Bhanusree Pola 2019-02-25 363 unsigned int transp, struct fb_info *info)
c296d5f9957c03 Thomas Petazzoni 2014-12-31 364 {
1c41494adf7aa6 Ming Yang 2016-07-17 365 unsigned int val;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 366 int ret = 1;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 367
b38c760ab0e1d7 Madhusudhanan Ravindran 2015-06-01 @368 dev_dbg(info->dev,
c296d5f9957c03 Thomas Petazzoni 2014-12-31 369 "%s(regno=%u, red=0x%X, green=0x%X, blue=0x%X, trans=0x%X)\n",
c296d5f9957c03 Thomas Petazzoni 2014-12-31 370 __func__, regno, red, green, blue, transp);
c296d5f9957c03 Thomas Petazzoni 2014-12-31 371
c296d5f9957c03 Thomas Petazzoni 2014-12-31 372 switch (info->fix.visual) {
c296d5f9957c03 Thomas Petazzoni 2014-12-31 373 case FB_VISUAL_TRUECOLOR:
c296d5f9957c03 Thomas Petazzoni 2014-12-31 374 if (regno < 16) {
c296d5f9957c03 Thomas Petazzoni 2014-12-31 375 u32 *pal = info->pseudo_palette;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 376
c296d5f9957c03 Thomas Petazzoni 2014-12-31 377 val = chan_to_field(red, &info->var.red);
c296d5f9957c03 Thomas Petazzoni 2014-12-31 378 val |= chan_to_field(green, &info->var.green);
c296d5f9957c03 Thomas Petazzoni 2014-12-31 379 val |= chan_to_field(blue, &info->var.blue);
c296d5f9957c03 Thomas Petazzoni 2014-12-31 380
c296d5f9957c03 Thomas Petazzoni 2014-12-31 381 pal[regno] = val;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 382 ret = 0;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 383 }
c296d5f9957c03 Thomas Petazzoni 2014-12-31 384 break;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 385 }
c296d5f9957c03 Thomas Petazzoni 2014-12-31 386 return ret;
c296d5f9957c03 Thomas Petazzoni 2014-12-31 387 }
c296d5f9957c03 Thomas Petazzoni 2014-12-31 388
:::::: The code at line 368 was first introduced by commit
:::::: b38c760ab0e1d7e051f13e31771514b5809de222 staging: fbtft: replace fbtft_dev_dbg with standard dev_dbg call
:::::: TO: Madhusudhanan Ravindran <mravindr@visteon.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-23 1:51 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=202601230916.VpgbAIF5-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=chintanlike@gmail.com \
--cc=deller@gmx.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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.